CVE-2026-25268

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-06. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

Memory Corruption when processing invalid HT40 channel layouts during dynamic channel switching operations.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (1)

Auto-updated Jul 6, 2026
No patch confirmed yet.
generic

Qualcomm Documentation

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

Vendor Advisories for CVE-2026-25268(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 12× in last 7d / 55× 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-07-27 11:24 UTCGHSA enrichment
  2. 2026-07-27 00:07 UTCEG score recompute
  3. 2026-07-27 00:06 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 12:47 UTCEG score recompute
  7. 2026-07-26 12:46 UTCGHSA enrichment
  8. 2026-07-24 14:17 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:07 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-19 14:31 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-18 10:04 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-17 04:58 UTCGHSA enrichment
  19. 2026-07-16 17:42 UTCGHSA enrichment
  20. 2026-07-16 17:03 UTCEPSS rescore
  21. 2026-07-16 17:03 UTCEPSS rescore
  22. 2026-07-16 06:25 UTCGHSA enrichment
  23. 2026-07-15 19:08 UTCGHSA enrichment
  24. 2026-07-15 07:51 UTCGHSA enrichment
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 30 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-14 20:35 UTCGHSA enrichment
  3. 2026-07-14 09:14 UTCGHSA enrichment
  4. 2026-07-13 22:30 UTCEPSS rescore
  5. 2026-07-13 21:58 UTCGHSA enrichment
  6. 2026-07-13 10:41 UTCGHSA enrichment
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-12 23:19 UTCGHSA enrichment
  10. 2026-07-12 12:02 UTCGHSA enrichment
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-12 00:45 UTCGHSA enrichment
  14. 2026-07-11 13:27 UTCGHSA enrichment
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-11 02:10 UTCGHSA enrichment
  17. 2026-07-10 14:51 UTCGHSA enrichment
  18. 2026-07-10 03:34 UTCGHSA enrichment
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 16:17 UTCGHSA enrichment
  21. 2026-07-09 05:00 UTCGHSA enrichment
  22. 2026-07-08 17:41 UTCGHSA enrichment
  23. 2026-07-08 15:15 UTCEPSS rescore
  24. 2026-07-08 15:15 UTCEPSS rescore
  25. 2026-07-08 06:24 UTCGHSA enrichment
  26. 2026-07-07 19:07 UTCGHSA enrichment
  27. 2026-07-07 13:46 UTCEPSS rescore
  28. 2026-07-07 07:48 UTCGHSA enrichment
  29. 2026-07-06 20:30 UTCEG score recompute
  30. 2026-07-06 20:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-25268?
CVE-2026-25268 is a high vulnerability published on July 6, 2026. Memory Corruption when processing invalid HT40 channel layouts during dynamic channel switching operations.
When was CVE-2026-25268 disclosed?
CVE-2026-25268 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25268 actively exploited?
CVE-2026-25268 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 99.9% of all scored CVEs.
What is the CVSS score of CVE-2026-25268?
CVE-2026-25268 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-25268?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25268, 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-25268

Explore →

Is Your Infrastructure Affected by CVE-2026-25268?

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

Start Free Scan →Browse All CVEs