# Docling Core: Insufficient validation of image reference URIs

Advisory record · `GHSA-j5xp-7m2f-49jv`

- **Identifiers:** `GHSA-j5xp-7m2f-49jv` · `CVE-2026-44019` · `PYSEC-2026-2456`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-73](https://cwe.mitre.org/data/definitions/73.html) · [CWE-400](https://cwe.mitre.org/data/definitions/400.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 3 Jun 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 3 Jun 2026, 21:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `docling-core` (PyPI): affected `>=2.5.0, <2.74.1`; fixed in `2.74.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Docling Core versions 2.5.0 up to but not including 2.74.1 accept local file:// image references and inline data: image content with no decoded-size limit. In applications that take untrusted image references, an attacker may be able to read local files the process can access or cause excessive memory use. Upgrade to docling-core 2.74.1 or later; until then, reject file: and data: image references from untrusted input and apply input size and memory limits.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0042, the 36th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:59 UTC: First seen by agentprime
- 31 Oct 2026, 14:59 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-j5xp-7m2f-49jv)

## Sources

- [GitHub Advisory Database: GHSA-j5xp-7m2f-49jv](https://github.com/advisories/GHSA-j5xp-7m2f-49jv)
- [OSV: GHSA-j5xp-7m2f-49jv](https://osv.dev/vulnerability/GHSA-j5xp-7m2f-49jv)
- <https://github.com/docling-project/docling-core/security/advisories/GHSA-j5xp-7m2f-49jv>
- <https://github.com/docling-project/docling-core>
- <https://github.com/docling-project/docling-core/releases/tag/v2.74.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-j5xp-7m2f-49jv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-j5xp-7m2f-49jv/>. Everything for agents: <https://agentprime.io/llms.txt>.
