Docling Core: Insufficient validation of image reference URIsGHSA-j5xp-7m2f-49jv
HIGHGHSA-j5xp-7m2f-49jv is a high-severity (CVSS 8.1) CWE-73 vulnerability in docling-core. A fix is available for docling-core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-j5xp-7m2f-49jv.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-j5xp-7m2f-49jv by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 390,400 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
docling-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
In versions >= 2.5.0, < 2.74.1, docling-core could allow local file:// image references and accepted inline data: content without a decoded-size limit.
In applications that accept untrusted image references, this may allow access to local files readable by the process or excessive memory use from large inline payloads.
Patches
Patched in docling-core 2.74.1.
The fix blocks local file URIs by default and adds a size limit for decoded inline image data.
Users should upgrade to:
docling-core>= 2.74.1
Workarounds
If upgrading is not immediately possible:
- reject
file:anddata:image references from untrusted input - allow only approved local or remote image sources
- apply input size and memory limits to processing workers
References
- Fix release:
v2.74.1
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | docling-core | ≥ 2.5.0&&< 2.74.1 | 2.74.1pip install --upgrade 'docling-core==2.74.1' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for docling-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update docling-core to 2.74.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j5xp-7m2f-49jv is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-j5xp-7m2f-49jv in your dependencies?
Find it across PyPI, including transitive dependencies.