Driftregion iso14229 before 0.10.1 contains an integer wraparound in Handle_0x38_RequestFileTransfer that lets unauthenticated attackers bypass the file path length check. Attackers can send a short RequestFileTransfer (SID 0x38) request with filePathAndNameLength 0xFFFC-0xFFFF, causing callbacks to read past the receive buffer, crashing targets or disclosing memory.
CVE-2026-111282
HIGHPre-NVD 8.28.2Trending — 4 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-10-16. A secondary CVSS source baseline 8.2; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.5%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.2
- EG Score
- 8.2HIGHhigh confidence
- EG Risk
- 68EG Risk 68/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity82% × 45%The EG Score, 8.2 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.5%
- EPSS %ILE
- 39th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 15, 2026
Last Modified
October 16, 2026
Advisory Details (6)
Auto-updated Oct 15, 2026🔬 Proof of concept available. Patch available. Sources: github, github_release.
Web page
iso14229 before 0.10.1 Out-of-Bounds Read via Handle_0x38_RequestFileTransfer | Advisories | VulnCheck
https://www.vulncheck.com/advisories/iso14229-before-0.10.1-out-of-bounds-read-via-handle-0x38-requestfiletransferWeb page
GitHub - driftregion/iso14229: ISO 14229 (UDS) server and client for embedded systems · GitHub
https://github.com/driftregion/iso14229GitHub release Patch Available
0.10.1+9e7c47e8
Patch available: driftregion/iso14229 0.10.1+9e7c47e8
https://github.com/driftregion/iso14229/releases/tag/0.10.1%2B9e7c47e8Web page
iso14229/src/server.c at 0.10.0 · driftregion/iso14229 · GitHub
https://github.com/driftregion/iso14229/blob/0.10.0/src/server.c#L1151-L1161GitHub advisoryMentions a patch (unverified)🟡 PoC Available
Integer overflow in Handle_0x38_RequestFileTransfer leads to heap out-of-bounds read via a 5-byte unauthenticated UDS request · Advisory · driftregion/iso14229 · GitHub
https://github.com/driftregion/iso14229/security/advisories/GHSA-ph4f-7v39-8hgmGitHub advisoryMentions a patch (unverified)🟡 PoC Available
Out-of-bounds read in `RequestFileTransfer` (SID 0x38) via `uint16_t` wraparound of the file-path length · Advisory · driftregion/iso14229 · GitHub
https://github.com/driftregion/iso14229/security/advisories/GHSA-5hgv-5fqg-8vcrVendor Advisories for CVE-2026-111282(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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.
- 2026-10-16 19:27 UTCEG score recompute
- 2026-10-16 19:27 UTCGHSA enrichmentGHSA-w2jf-rrfp-47w9 · GitHub severity HIGH · GitHub CVSS 8.2
- 2026-10-16 19:10 UTCEG score recompute
- 2026-10-16 19:09 UTCGHSA enrichmentGHSA-w2jf-rrfp-47w9 · GitHub severity HIGH · GitHub CVSS 8.2
- 2026-10-16 18:47 UTCEG score recompute
- 2026-10-16 18:47 UTCGHSA enrichmentGHSA-w2jf-rrfp-47w9 · GitHub severity HIGH · GitHub CVSS 8.2
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-15 22:36 UTCEG score recompute
- 2026-10-15 21:51 UTCEG score recomputeFirst assessed: 8.2 HIGH
- 2026-10-15 21:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-111282?
CVE-2026-111282 is a high-severity vulnerability; its CVE record was published on October 15, 2026. Driftregion iso14229 before 0.10.1 contains an integer wraparound in Handle0x38RequestFileTransfer that lets unauthenticated attackers bypass the file path length check. Attackers can send a short RequestFileTransfer (SID 0x38) request with filePathAndNameLength 0xFFFC-0xFFFF, causing callbacks to…
When was CVE-2026-111282 made public?
CVE-2026-111282 was made public on September 27, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 15, 2026. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-111282 actively exploited?
CVE-2026-111282 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-111282?
CVE-2026-111282 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-111282?
A fix for CVE-2026-111282 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-111282 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-111282
Is Your Infrastructure Affected by CVE-2026-111282?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.