CVE-2026-124553

waiting for further signalsZero needs more public information before it can validate it.

GHSA-2w74-49x3-cmf5 ↗EUVD-2026-119609 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
funstory-ai BabelDOC >= 0.3.61, < 0.7.0
fixed in 0.7.0
ETK-2026-3898Zero's internal tracking ID, independent of the CVE number., permanent identifier
2d 14h 50msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h57m
0
+4h
+6h
+8h
+10h
+12h

description

BabelDOC versions 0.3.61 through earlier than 0.7.0 can consume excessive CPU and memory while processing PDFs with malformed font character-mapping data. An attacker can stall translation workers by submitting a crafted PDF, where the deployment accepts PDFs from the attacker.

mitigation

Upgrade BabelDOC to version 0.7.0 or later. Until upgrades are complete, restrict untrusted PDF submissions to translation workers and enforce processing resource limits where possible.

fixed in 0.7.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.54%45th percentile
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-08 14:12Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-08 14:12Z
    ghsa: trigger signal, started the run
  2. 2026-11-08 14:12Z

this entry in the feed

GET /api/v1/feed/CVE-2026-124553

{
  "etk_id": "ETK-2026-3898",
  "cve_id": "CVE-2026-124553",
  "display_id": "CVE-2026-124553",
  "ghsa_id": "GHSA-2w74-49x3-cmf5",
  "euvd_id": "EUVD-2026-119609",
  "status": "published",
  "anchor_state": "anchored",
  "title": "CPU and memory exhaustion in BabelDOC PDF processing",
  "summary": "BabelDOC versions 0.3.61 through earlier than 0.7.0 can consume excessive CPU and memory while processing PDFs with malformed font character-mapping data. An attacker can stall translation workers by submitting a crafted PDF, where the deployment accepts PDFs from the attacker.",
  "mitigation": "Upgrade BabelDOC to version 0.7.0 or later. Until upgrades are complete, restrict untrusted PDF submissions to translation workers and enforce processing resource limits where possible.",
  "vendor": "funstory-ai",
  "product": "BabelDOC",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.3.61, < 0.7.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.7.0"
      ],
      "package_name": "BabelDOC",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0054,
  "epss_percentile": 0.4583,
  "epss_asof": "2026-11-09",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.682396,
  "t0_at": "2026-11-08T14:12:44.813000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-08T14:12:44.813000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T14:12:44.813000+00:00",
      "url": "https://github.com/advisories/GHSA-2w74-49x3-cmf5"
    }
  }
}

published 2026-11-08 15:54Z
last change 2026-11-11 05:47Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.