Local file disclosure and memory exhaustion via ImageRef
Published Jul 16, 2026 · Updated Jul 16, 2026
Path traversal and resource consumption in Docling Core 2.5.0 through 2.74.0 allow remote attackers to read local files or exhaust memory. The ImageRef.pil_image property passes file URI paths directly to PILImage.open and base64-decodes data URI bodies without limiting decoded length. Exploitation requires a consuming application to accept attacker-controlled image references and resolve the image; disclosure is limited to process-readable files.
Summary
What happened
Path traversal and resource consumption in Docling Core 2.5.0 through 2.74.0 allow remote attackers to read local files or exhaust memory. The ImageRef.pil_image property passes file URI paths directly to PILImage.open and base64-decodes data URI bodies without limiting decoded length. Exploitation requires a consuming application to accept attacker-controlled image references and resolve the image; disclosure is limited to process-readable files.
The record
- CVE
- CVE-2026-44019
- Published
- Jul 16, 2026
- Updated
- Jul 16, 2026
- Vendor
- Docling Project
- Product
- Docling Core
- Classifications
- CWE-400, CWE-73, T1499.003, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2026CVE publishedPublication date reported by the CVE source.
- Jul 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.5.0, < 2.74.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo