CVE-2026-24073

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.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: 7.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 decode statistics due to insufficient validation of offset against structure size.

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

Published

September 17, 2026

Last Modified

September 22, 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-24073(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 25× in last 7d / 35× 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-25 06:51 UTCGHSA enrichment
  2. 2026-09-24 19:04 UTCEG score recompute
  3. 2026-09-24 19:04 UTCGHSA enrichment
  4. 2026-09-24 14:03 UTCEPSS rescore
  5. 2026-09-24 07:17 UTCGHSA enrichment
  6. 2026-09-23 19:30 UTCEG score recompute
  7. 2026-09-23 19:30 UTCGHSA enrichment
  8. 2026-09-23 07:40 UTCGHSA enrichment
  9. 2026-09-22 19:54 UTCGHSA enrichment
  10. 2026-09-22 17:40 UTCEG score recompute
  11. 2026-09-22 17:40 UTCGHSA enrichment
  12. 2026-09-22 05:42 UTCEG score recompute
  13. 2026-09-22 05:42 UTCGHSA enrichment
  14. 2026-09-21 17:56 UTCGHSA enrichment
  15. 2026-09-21 06:10 UTCEG score recompute
  16. 2026-09-21 06:10 UTCGHSA enrichment
  17. 2026-09-20 20:15 UTCEPSS rescore
  18. 2026-09-20 18:22 UTCGHSA enrichment
  19. 2026-09-20 06:35 UTCGHSA enrichment
  20. 2026-09-19 18:42 UTCEG score recompute
  21. 2026-09-19 18:42 UTCGHSA enrichment
  22. 2026-09-19 06:55 UTCEG score recompute
  23. 2026-09-19 06:55 UTCGHSA enrichment
  24. 2026-09-18 19:27 UTCEPSS rescore
  25. 2026-09-18 19:09 UTCGHSA enrichment
Show 10 more
  1. 2026-09-18 12:55 UTCGHSA enrichment
  2. 2026-09-18 01:09 UTCEG score recompute
  3. 2026-09-18 01:09 UTCGHSA enrichment
  4. 2026-09-17 13:22 UTCEG score recompute
  5. 2026-09-17 13:22 UTCGHSA enrichment
  6. 2026-09-17 13:04 UTCEG score recompute
  7. 2026-09-17 13:04 UTCGHSA enrichment
  8. 2026-09-17 05:22 UTCEG score recompute
  9. 2026-09-17 04:29 UTCEG score recompute
  10. 2026-09-17 04:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-24073?
CVE-2026-24073 is a high vulnerability published on September 17, 2026. Memory corruption when processing decode statistics due to insufficient validation of offset against structure size.
When was CVE-2026-24073 disclosed?
CVE-2026-24073 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24073 actively exploited?
CVE-2026-24073 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 100.0% of all scored CVEs.
What is the CVSS score of CVE-2026-24073?
CVE-2026-24073 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-24073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24073, 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-24073

Explore →

Is Your Infrastructure Affected by CVE-2026-24073?

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

Book a Demo →Browse All CVEs