CVE-2026-116488

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreHIGH confidence

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

Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-26. A secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: GitHub Security Advisory, a secondary CVSS source
Trending — 5 sources updated this week

Also known asEUVD-2026-109815 (ENISA EUVD) · GHSA-6rvq-9jq9-prp3 (GitHub Security Advisories)Source: ENISA EUVD

6.8EG
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.4%CVSS: 6.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

NXP MCUXpresso SDK USB middleware (mcuxsdk-middleware-usb) before 2.13.0 contains a heap buffer overflow in host audio, video and CDC class drivers that trust device-supplied bNumEndpoints and bLength values. A malicious USB device can supply crafted descriptors that write endpoint entries past the fixed-size epList array, corrupting heap memory for code execution or denial of service.

CVSS v3
6.8
EG Score
6.8MEDIUMhigh confidence
EG Risk
31
EG Risk 31/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)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
The CVE's CVSS v4.0 attack vector is Physical: an attacker must touch each system, so exploitation cannot be automated (no).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CVSS v4.0 attack vector Physical) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.4%
EPSS %ILE
31st
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 (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. 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: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: 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).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CVSS v4.0 attack vector Physical) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CVSS v4.0 attack vector Physical) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). 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 26, 2026

Last Modified

October 26, 2026

Advisory Details (7)

Auto-updated Oct 26, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

NXP MCUXpresso SDK USB Middleware before 2.13.0 Heap Overflow via Host Class Drivers | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nxp-mcuxpresso-sdk-usb-middleware-before-2.13.0-heap-overflow-via-host-class-drivers
Web page

GitHub - nxp-mcuxpresso/mcuxsdk-middleware-usb: MCUXpresso SDK USB stack Middleware · GitHub

https://github.com/nxp-mcuxpresso/mcuxsdk-middleware-usb
Web page

Release Notes — MCUXpresso SDK Documentation

https://mcuxpresso.nxp.com/mcuxsdk/latest/release/index.html#release-highlights
Web page

mcuxsdk-middleware-usb/host/class/usb_host_audio.c at release/26.06.00 · nxp-mcuxpresso/mcuxsdk-middleware-usb · GitHub

https://github.com/nxp-mcuxpresso/mcuxsdk-middleware-usb/blob/release/26.06.00/host/class/usb_host_audio.c#L517
GitHub commit

commit f615b03e302f (nxp-mcuxpresso/mcuxsdk-middleware-usb)

Fix landed in nxp-mcuxpresso/mcuxsdk-middleware-usb commit f615b03e302f — awaiting tagged release

https://github.com/nxp-mcuxpresso/mcuxsdk-middleware-usb/commit/f615b03e302f0c58de5bf1cfeb31dfb85a2e514a
GitHub commit

commit 6a1d1a7c3202 (nxp-mcuxpresso/mcuxsdk-middleware-usb)

Fix landed in nxp-mcuxpresso/mcuxsdk-middleware-usb commit 6a1d1a7c3202 — awaiting tagged release

https://github.com/nxp-mcuxpresso/mcuxsdk-middleware-usb/commit/6a1d1a7c32026e6d83504415931c4ae97ef7b7a1
GitHub commit

commit 264b8e6849e6 (nxp-mcuxpresso/mcuxsdk-middleware-usb)

Fix landed in nxp-mcuxpresso/mcuxsdk-middleware-usb commit 264b8e6849e6 — awaiting tagged release

https://github.com/nxp-mcuxpresso/mcuxsdk-middleware-usb/commit/264b8e6849e609abd8e2b045bc7786818b0d2bbc

Vendor Advisories for CVE-2026-116488(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 7× in last 7d / 7× 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-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-26 19:01 UTCEG score recompute
  3. 2026-10-26 19:01 UTCGHSA enrichmentGHSA-6rvq-9jq9-prp3 · GitHub severity HIGH · GitHub CVSS 6.8
  4. 2026-10-26 15:01 UTCENISA EUVD ID recordedEUVD-2026-109815 · Source: ENISA EUVD
  5. 2026-10-26 14:44 UTCEG score recompute
  6. 2026-10-26 14:02 UTCEG score recomputeFirst assessed: 6.8 MEDIUM
  7. 2026-10-26 14:00 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-116488?
CVE-2026-116488 is a medium-severity vulnerability; its CVE record was published on October 26, 2026. NXP MCUXpresso SDK USB middleware (mcuxsdk-middleware-usb) before 2.13.0 contains a heap buffer overflow in host audio, video and CDC class drivers that trust device-supplied bNumEndpoints and bLength values. A malicious USB device can supply crafted descriptors that write endpoint entries past the…
When was CVE-2026-116488 made public?
CVE-2026-116488 was made public on September 7, 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 26, 2026. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-116488 actively exploited?
CVE-2026-116488 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-116488?
CVE-2026-116488 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-116488?
An upstream fix for CVE-2026-116488 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-116488 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-116488

Explore →

Is Your Infrastructure Affected by CVE-2026-116488?

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