CVE-2026-105742

LOWNVD 5.33.7
EchelonGraph scoreMEDIUM confidence

“▼” beside the score: it is lower than NVD's CVSS score.

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-10-07. NVD baseline CVSS 5.3; sources differ by 1.6.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-92802 (ENISA EUVD) · GHSA-p3fw-7699-7926 (GitHub Security Advisories) · PYSEC-2026-4189 (OSV.dev) · PYSEC-2026-4212 (OSV.dev)Source: ENISA EUVD

3.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.3Exploit: No code on recordExposed 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.95.0 until 2.132.0, the HTML image resource loader in docling/backend/utils/image_resource_loader.py forwards headers configured through the HTMLBackendOptions.headers setting to every remote image URL named by an untrusted document when enable_remote_fetch=True and fetch_images=True. The loader does not restrict those credentials to the source document's origin, allowing requests that carry custom headers such as API keys and cookies to follow cross-origin redirects and expose the caller's configured credentials to a document author. The default configuration is not affected because remote fetching and configured headers are required. This issue is fixed in 2.132.0.

CVSS v3
5.3
EG Score
3.7LOWmedium confidence
EG Risk
33
EG Risk 33/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)
Severity37% × 45%
Impact severity (EG Severity): CVSS 3.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.3%
EPSS %ILE
17th
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 (3.7): severity, escalated by confirmed exploitation. This CVE's 3.7 is its impact severity (EG Severity), not escalated.

EG Severity
3.7 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 low or medium mission impact; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

Configured HTTP headers sent to every remote image host named by a document · Advisory · docling-project/docling · GitHub

https://github.com/docling-project/docling/security/advisories/GHSA-p3fw-7699-7926
GitHub release Patch Available

Release v2.132.0 (docling-project/docling)

Patch available: docling-project/docling v2.132.0

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

fix(html): validate every resolved address and scope fetch headers to the source origin

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

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

commit 5e469137f275 (docling-project/docling)

Patch available: docling-project/docling v2.132.0 (contains commit 5e469137f275)

https://github.com/docling-project/docling/commit/5e469137f275ffc443306a30d12a3a45bceb80fb

Vendor Advisories for CVE-2026-105742(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipdocling @ 2.132.0 (fixes >= 2.95.0, < 2.132.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFix by version rangeDependents
docling2.100.0 ... 2.99.0 (44 versions)
  • 2.95.0 up to 2.132.0: fixed in 2.132.0
—
docling-slim2.100.0 ... 2.99.0 (44 versions)
  • 2.95.0 up to 2.132.0: fixed in 2.132.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 48× 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.3% · 17th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-p3fw-7699-7926 · GitHub severity LOW · GitHub CVSS 3.7
  4. 2026-11-01 08:00 UTCEG score recompute▼ 1.60
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-31 11:55 UTCOSV refresh
  7. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-25 14:55 UTCEG score recompute
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  16. 2026-10-23 09:13 UTCEG score recompute
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  19. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  22. 2026-10-18 05:08 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  24. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
Show 23 more
  1. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-10-12 16:39 UTCEG score recompute
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-10-11 20:15 UTCEG score recompute
  6. 2026-10-11 16:45 UTCEG score recompute
  7. 2026-10-11 15:01 UTCEG score recompute
  8. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-10-10 17:45 UTCEG score recompute
  11. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-10-08 19:40 UTCEG score recompute
  13. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-07 20:01 UTCEG score recompute▲ 1.60
  16. 2026-10-07 20:00 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  17. 2026-10-06 15:23 UTCEG score recompute
  18. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-10-06 14:32 UTCEG score recompute
  20. 2026-10-06 14:00 UTCEG score recompute
  21. 2026-10-05 22:22 UTCEG score recompute
  22. 2026-10-05 21:33 UTCEG score recomputeFirst assessed: 3.7 LOW
  23. 2026-10-05 21:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-105742?
CVE-2026-105742 is a low-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.95.0 until 2.132.0, the HTML image resource loader in docling/backend/utils/image_resource_loader.py forwards headers configured through the…
When was the CVE record for CVE-2026-105742 published?
The CVE record for CVE-2026-105742 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-105742 actively exploited?
CVE-2026-105742 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105742?
CVE-2026-105742 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 3.7 (LOW).
How do I remediate CVE-2026-105742?
A fix for CVE-2026-105742 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-105742 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-105742?

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