BabelDOC from 0.3.61 before 0.7.0 Denial of Service via ToUnicode CMap Parsing
BabelDOC 0.3.61 up to but not including 0.7.0 is affected when it parses PDFs with an embedded ToUnicode CMap. The fix is in 0.7.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.7.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.7.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
BabelDOC from 0.3.61 before 0.7.0 contains a resource exhaustion vulnerability that allows remote attackers to exhaust CPU and memory by supplying unbounded bfrange and cidrange spans. Attackers can submit a crafted PDF whose embedded ToUnicode CMap declares a huge range, driving billions of loop iterations and stalling the translation worker.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.7.0.
Workaround: Isolate parsing in a subprocess or container with hard memory and CPU limits and a timeout; this reduces known exploit preconditions but is not equivalent to the fix
Timeline
- CVE published
- First seen by cve.now
Affected versions
- funstory-ai BabelDOC
From 0.3.61 · fixed in 0.7.0
Evidence 6
- Advisory
- Patch
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124553
Is CVE-2026-124553 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Unbounded bfrange and cidrange spans in ToUnicode CMap data can exhaust CPU and memory. This stalls the translation worker, which is a denial of service.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-124553?
BabelDOC: from 0.3.61 before 0.7.0.Source: cve.now feed data
Am I affected, and how do I check?
BabelDOC versions from 0.3.61 up to but not including 0.7.0 are in the affected range. The affected code path is font handling that passes /ToUnicode stream data into CMapParser, so check the installed BabelDOC version against that range.Source: vulncheck.com, github.com
How do I fix CVE-2026-124553?
Upgrade BabelDOC to 0.7.0 or later, which is the fixed release. If an upgrade is not possible, isolate PDF parsing in a subprocess or container with hard memory and CPU limits and a timeout; this reduces the conditions for the problem but is not equivalent to the fix.Source: vulncheck.com, github.com