# CVE-2026-112310: docling-core 2.5.0 before 2.103.0 Local File Disclosure via Plain Path ImageRef

> Attackers can read local image files by supplying plain filesystem paths in ImageRef URIs within crafted documents, leading to information disclosure.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-jx5c-6gmw-72m3

## What is CVE-2026-112310?

CVE-2026-112310 is a medium-severity path traversal vulnerability in docling-project docling-core, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

docling-core 2.5.0 before 2.103.0 contains a local file disclosure vulnerability that allows attackers to read local images by supplying plain filesystem paths in ImageRef URIs, bypassing the allow_image_file_uri gate. Attackers can submit crafted DoclingDocument JSON or YAML that, when exported with ImageRefMode.EMBEDDED or rendered to HTML, embeds readable local image files as base64 and reveals path existence.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-112310?


## How do I fix CVE-2026-112310?

No fix has been published for CVE-2026-112310 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112310 being exploited?

There is no known exploitation of CVE-2026-112310 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112310 and fix it if it is affected.

What it is: CVE-2026-112310 is a medium-severity path traversal vulnerability in docling-project docling-core, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-112310 in the wild and no public exploit code.

Affected product: docling-project docling-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112310/ (Markdown: https://insights.sbomify.com/CVE-2026-112310/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112310
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112310
- OSV: https://osv.dev/vulnerability/CVE-2026-112310

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112310/
Summaries are generated and may contain mistakes; the official description above is the record.