CVE-2026-25261

MEDIUMPre-NVD 6.76.7—
EchelonGraph scoreHIGH confidence

Score 6.7 from GitHub Security Advisory published 2026-09-17. a secondary CVSS source baseline 6.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Memory corruption while processing rear sensor IOCTL calls.

CVSS v3
6.7
EG Score
6.7(high)
EG Risk
30(Track)
EG Risk 30/100SSVC: Track

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
Severity67% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 17, 2026
No patch confirmed yet.
generic

Qualcomm Documentation

https://docs.qualcomm.com/product/publicresources/securitybulletin/september-2026-bulletin.html

Vendor Advisories for CVE-2026-25261(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 11× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-18 19:09 UTCGHSA enrichment
  3. 2026-09-18 13:58 UTCEG score recompute
  4. 2026-09-18 13:58 UTCGHSA enrichment
  5. 2026-09-17 15:22 UTCEG score recompute
  6. 2026-09-17 15:22 UTCGHSA enrichment
  7. 2026-09-17 14:45 UTCEG score recompute
  8. 2026-09-17 14:45 UTCGHSA enrichment
  9. 2026-09-17 05:22 UTCEG score recompute
  10. 2026-09-17 04:29 UTCEG score recompute
  11. 2026-09-17 04:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-25261?
CVE-2026-25261 is a medium vulnerability published on September 17, 2026. Memory corruption while processing rear sensor IOCTL calls.
When was CVE-2026-25261 disclosed?
CVE-2026-25261 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25261 actively exploited?
CVE-2026-25261 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-25261?
CVE-2026-25261 has a CVSS v3 base score of 6.7 (NVD).
How do I remediate CVE-2026-25261?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25261, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-25261?

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

Start Free Scan →Browse All CVEs