CVE-2026-21366

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-04. 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 while processing a packet with a size close to the maximum allowed value.

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

August 4, 2026

Last Modified

August 6, 2026

Advisory Details (1)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

Qualcomm Documentation

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-21366?
CVE-2026-21366 is a high vulnerability published on August 4, 2026. Memory corruption while processing a packet with a size close to the maximum allowed value.
When was CVE-2026-21366 disclosed?
CVE-2026-21366 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21366 actively exploited?
CVE-2026-21366 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-21366?
CVE-2026-21366 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-21366?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21366, 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-21366

Explore →

Is Your Infrastructure Affected by CVE-2026-21366?

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

Start Free Scan →Browse All CVEs