CVE-2026-105746

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-92808 (ENISA EUVD) · PYSEC-2026-4193 (OSV.dev)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.83.0 until 2.131.0, the KServeV2OcrModel class defined in docling/models/stages/ocr/kserve_v2_ocr_model.py sends page images to its configured endpoint without checking the pipeline_options.enable_remote_services setting, even when the caller sets that policy control to false. The StandardPdfPipeline._make_ocr_model method also fails to pass the flag into the OCR factory, allowing remote OCR processing in configurations that rely on remote services being disabled. The destination is configured by the caller rather than selected by an attacker. This issue is fixed in 2.131.0.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 5, 2026

Last Modified

October 7, 2026

Advisory Details (4)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

KServe v2 OCR engine does not enforce enable_remote_services · Advisory · docling-project/docling · GitHub

https://github.com/docling-project/docling/security/advisories/GHSA-h42j-9hcc-3cwc
GitHub release Patch Available

Release v2.131.0 (docling-project/docling)

Patch available: docling-project/docling v2.131.0

https://github.com/docling-project/docling/releases/tag/v2.131.0
GitHub pull request Patch Available

fix(ocr): require enable_remote_services for the KServe v2 OCR engine

Patch available: docling-project/docling v2.131.0 (PR #4418 merged 2026-09-29)

https://github.com/docling-project/docling/pull/4418
GitHub commit Patch Available

commit 7d6d0c4810df (docling-project/docling)

Patch available: docling-project/docling v2.131.0 (contains commit 7d6d0c4810df)

https://github.com/docling-project/docling/commit/7d6d0c4810dff4885017c53890be6dc5a22ca68b

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
docling2.100.0 ... 2.99.0 (55 versions)
  • 2.83.0 up to 2.131.0: fixed in 2.131.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-10-31 11:55 UTCOSV refresh
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-10-25 14:55 UTCEG score recompute
  12. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-10-23 09:13 UTCEG score recompute
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  16. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  17. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  19. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-10-18 05:08 UTCEG score recompute
  21. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  22. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  23. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  24. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
Show 22 more
  1. 2026-10-12 16:39 UTCEG score recompute
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-11 20:15 UTCEG score recompute
  4. 2026-10-11 18:27 UTCEG score recompute
  5. 2026-10-11 15:01 UTCEG score recompute
  6. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-10 23:26 UTCEG score recompute
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-09 22:04 UTCEG score recompute
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-08 20:42 UTCEG score recompute
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-10-07 19:21 UTCEG score recompute▲ 3.10
  15. 2026-10-07 19:19 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  16. 2026-10-06 17:19 UTCEG score recompute
  17. 2026-10-06 16:52 UTCEG score recompute
  18. 2026-10-06 15:23 UTCEG score recompute
  19. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-10-05 22:20 UTCEG score recompute
  21. 2026-10-05 21:46 UTCEG score recomputeFirst assessed: 2.2 LOW
  22. 2026-10-05 21:45 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-105746?
CVE-2026-105746 is a medium-severity vulnerability; its CVE record was published on October 5, 2026. Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.83.0 until 2.131.0, the KServeV2OcrModel class defined in docling/models/stages/ocr/kserve_v2_ocr_model.py sends page images to its configured endpoint without…
When was the CVE record for CVE-2026-105746 published?
The CVE record for CVE-2026-105746 was published on October 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2026-105746 actively exploited?
CVE-2026-105746 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105746?
CVE-2026-105746 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-105746?
A fix for CVE-2026-105746 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-105746

Explore →

Is Your Infrastructure Affected by CVE-2026-105746?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs