Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-44019: CWE-73: External Control of File Name or Path in docling-project docling-core

0
High
VulnerabilityCVE-2026-44019cvecve-2026-44019cwe-73cwe-400
Published: 07/16/2026 (07/16/2026, 20:50:08 UTC)
Source: CVE Database V5
Vendor/Project: docling-project
Product: docling-core

Description

Docling-core versions from 2.5.0 up to but not including 2.74.1 contain a vulnerability where local file:// image references and inline data: content without a decoded-size limit are allowed. This can lead to unauthorized local file access or excessive memory consumption. The issue has been fixed in version 2.74.1.

CVSS v3.1

Score 8.1high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H

Affected software

GitHub Actionsmore threats →ai
docling-project/docling-core
pkg:github/docling-project/docling-core
Affected versions
>=2.5.0 <2.74.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/16/2026, 21:32:43 UTC

Technical Analysis

Docling-core, a document processing library, in versions >=2.5.0 and <2.74.1, improperly handles local file:// image references and inline data: content without enforcing a decoded-size limit. This flaw can enable an attacker to access local files readable by the process or cause excessive memory use due to large inline payloads. The vulnerability is identified as CWE-73 (External Control of File Name or Path) and CWE-400 (Uncontrolled Resource Consumption). The vulnerability has been resolved in version 2.74.1.

Potential Impact

An attacker supplying untrusted image references can potentially read local files accessible by the application process, leading to confidentiality breaches. Additionally, the lack of a decoded-size limit on inline data can cause excessive memory consumption, potentially resulting in denial of service conditions.

Mitigation Recommendations

Upgrade docling-core to version 2.74.1 or later, where this vulnerability has been fixed. No other mitigation is indicated or required according to the available data.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-05-04T21:24:36.506Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a594a9a68715ace43b94b92

Added to database: 07/16/2026, 21:18:18 UTC

Last enriched: 07/16/2026, 21:32:43 UTC

Last updated: 07/17/2026, 03:02:16 UTC

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses