CVE-2026-44023
Docling Core has unsafe remote filename resolution
Docling Core defines core data types and transformations for the document processing application Docling. In versions 1.5.0 and above, prior to 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner. In applications that accept untrusted URLs, this could allow SSRF attacks targeting local files outside the user-defined cache directory. This issue has been fixed in version 2.74.1.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
Exploit likelihood
What each source reports
CVE List Score used
Docling Core has unsafe remote filename resolution
Docling Core defines core data types and transformations for the document processing application Docling. In versions 1.5.0 and above, prior to 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner. In applications that accept untrusted URLs, this could allow SSRF attacks targeting local files outside the user-defined cache directory. This issue has been fixed in version 2.74.1.
- Record
CVE-2026-44023- CVSS 3.1
- 8.6 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L - Weakness
- CWE-22, CWE-918
- Updated
- 2026-11-02
EUVDEUVD-2026-45043
Docling Core defines core data types and transformations for the document processing application Docling. In versions 1.5.0 and above, prior to 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner. In applications that accept untrusted URLs, this could allow SSRF attacks targeting local files outside the user-defined cache directory. This issue has been fixed in version 2.74.1.
- Record
EUVD-2026-45043- CVSS 3.1
- 8.6 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-jmmv-h3mp-59v8
Docling Core: Unsafe remote filename resolution
Impact
In versions >= 1.5.0, < 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner.
In applications that accept untrusted URLs, this could allow SSRF attacks targeting local files outside the user-defined cache directory.
Patches
Patched in docling-core 2.74.1.
The fix adds stricter validation for remote destinations and normalizes server-provided filenames before use.
Users should upgrade to:
docling-core>= 2.74.1
Workarounds
If upgrading is not immediately possible, avoid passing untrusted URLs into remote fetch functionality.
References
- Fix release:
v2.74.1
- Record
GHSA-jmmv-h3mp-59v8- CVSS 3.1
- 8.6 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L - Weakness
- CWE-22, CWE-918
- Updated
- 2026-11-02
NVD
Docling Core defines core data types and transformations for the document processing application Docling. In versions 1.5.0 and above, prior to 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner. In applications that accept untrusted URLs, this could allow SSRF attacks targeting local files outside the user-defined cache directory. This issue has been fixed in version 2.74.1.
- Record
CVE-2026-44023- CVSS 3.1
- 8.6 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L - Weakness
- CWE-22, CWE-918
- Updated
- 2026-11-02
OSV
Docling Core has unsafe remote filename resolution
Docling Core defines core data types and transformations for the document processing application Docling. In versions 1.5.0 and above, prior to 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner. In applications that accept untrusted URLs, this could allow SSRF attacks targeting local files outside the user-defined cache directory. This issue has been fixed in version 2.74.1.
- Record
CVE-2026-44023- CVSS 3.1
- 8.6 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L - Weakness
- CWE-22, CWE-918
- Updated
- 2026-11-02
OSVGHSA-jmmv-h3mp-59v8
Docling Core: Unsafe remote filename resolution
Impact
In versions >= 1.5.0, < 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner.
In applications that accept untrusted URLs, this could allow SSRF attacks targeting local files outside the user-defined cache directory.
Patches
Patched in docling-core 2.74.1.
The fix adds stricter validation for remote destinations and normalizes server-provided filenames before use.
Users should upgrade to:
docling-core>= 2.74.1
Workarounds
If upgrading is not immediately possible, avoid passing untrusted URLs into remote fetch functionality.
References
- Fix release:
v2.74.1
- Record
GHSA-jmmv-h3mp-59v8- CVSS 3.1
- 8.6 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L - Weakness
- CWE-22, CWE-918
- Updated
- 2026-11-02
OSVPYSEC-2026-2457
Docling Core: Unsafe remote filename resolution
Impact
In versions >= 1.5.0, < 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner.
In applications that accept untrusted URLs, this could allow SSRF attacks targeting local files outside the user-defined cache directory.
Patches
Patched in docling-core 2.74.1.
The fix adds stricter validation for remote destinations and normalizes server-provided filenames before use.
Users should upgrade to:
docling-core>= 2.74.1
Workarounds
If upgrading is not immediately possible, avoid passing untrusted URLs into remote fetch functionality.
References
- Fix release:
v2.74.1
- Record
PYSEC-2026-2457- CVSS 3.1
- 8.6 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L - Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
docling-corePyPI |
1.5.0 up to 2.74.1 | 2.74.1 |
docling-corePyPI |
1.5.0 up to 2.74.1, plus listed versions 1.6.01.6.11.6.21.6.31.7.0 Show 45 moreShow less1.7.11.7.22.0.02.0.12.1.02.10.02.11.02.12.02.12.12.13.02.13.12.14.02.15.02.15.12.16.02.16.12.17.02.17.12.17.22.18.02.18.12.19.02.19.12.2.02.2.12.2.22.2.32.20.02.21.02.21.12.21.22.22.02.23.02.23.12.23.22.23.32.24.02.24.12.25.02.26.02.26.12.26.22.26.32.26.42.27.0 |
2.74.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-44023 is a high vulnerability (CVSS 8.6) in Docling Docling-core, published June 3, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.43%, the 37th percentile. Fixed in docling-core 2.74.1.
References
github.com/docling-project/docling-core/security/advisories/GHSA-jmmv-h3mp-59v8
nvd.nist.gov/vuln/detail/CVE-2026-44023
pypi.org/project/docling-core
Left out here: 87 versions. The JSON record has them.