Medium

CVE-2026-112310 — docling-core through 2.102.0 Local File Disclosure via Plain Path ImageRef

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.

Published Oct 19, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.3% (30-day exploitation probability)+4
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.34%

ahead of 26% of scored CVEs · Oct 23, 2026

Affects

Docling-project

Docling-core

CVSS base

4.3

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Docling-project Docling-core).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Docling-project	Docling-core	≥ 2.5.0 and < 2.103.0	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.3	CVSS 4.0	Medium	—	—	disclosure@vulncheck.com via NIST National Vulnerability Database
5.3	CVSS 4.0	Medium	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP
4.3	CVSS 3.1	Medium	2.8	1.4	disclosure@vulncheck.com via NIST National Vulnerability Database
4.3	CVSS 3.1	Medium	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-73

Other CVEs with this weakness →

EPSS over time FIRST

Oct 20, 2026 → Oct 23, 2026 · 4 reading(s) · max 0.34%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Source status changed · Received → Deferred
Oct 19, 2026 · NIST National Vulnerability Database
Affected products removed · 1
Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
Affected products added · docling-project/docling-core
Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
Affected products added · docling-project/docling-core
Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 19, 2026
CVSS changed · 4.3
Oct 19, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 19, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 19, 2026 · NIST National Vulnerability Database
CVE published
Oct 19, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

2× Official description updated · Oct 19, 2026 – Oct 19, 2026
1× References added · Oct 19, 2026 – Oct 19, 2026

References

7 on the record

github.com/docling-project/docling-core/commit/f952fc5d4c68fb673043c7c9f9c439005
patch, CVE Program (cve.org) e CISA ADP
github.com/docling-project/docling-core/pull/900
patch, issue-tracking, NIST National Vulnerability Database
github.com/docling-project/docling-core/blob/v2.102.0/docling_core/types/doc/doc
technical-description, NIST National Vulnerability Database
www.vulncheck.com/advisories/docling-core-through-2.102.0-local-file-disclosure-via-pla
third-party-advisory, NIST National Vulnerability Database
github.com/docling-project/docling-core/releases/tag/v2.103.0
release-notes, CVE Program (cve.org) e CISA ADP
github.com/docling-project/docling-core/blob/v2.102.0/docling_core/types/doc/com
technical-description, NIST National Vulnerability Database
github.com/docling-project/docling-core/security/advisories/GHSA-jx5c-6gmw-72m3
vendor-advisory, CVE Program (cve.org) e CISA ADP

Elsewhere on this site

Docling-project
every CVE for this vendor

CWE-73
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-44023 Docling Core has unsafe remote filename resolution Jul 16, 2026
High CVE-2026-44019 Docling Core has insufficient validation of image reference URIs Jul 16, 2026
Critical CVE-2026-24009 Docling Core vulnerable to Remote Code Execution via unsafe PyYAML usage Jan 22, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-112310 is "docling-core through 2.102.0 Local File Disclosure via Plain Path ImageRef", rated Medium. It affects Docling-core (Docling-project); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.3 describes technical severity. EPSS 0.34% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.