CVE-2026-21379

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-06. 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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

Memory Corruption when allocating memory with sizes that exceed 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
0.1%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (1)

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

Qualcomm Documentation

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

Vendor Advisories for CVE-2026-21379(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 / 36× 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-23 03:06 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 20:50 UTCGHSA enrichment
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-16 08:11 UTCGHSA enrichment
  11. 2026-07-15 19:32 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 06:53 UTCGHSA enrichment
  15. 2026-07-14 18:13 UTCGHSA enrichment
  16. 2026-07-14 05:34 UTCGHSA enrichment
  17. 2026-07-13 16:55 UTCGHSA enrichment
  18. 2026-07-13 04:16 UTCGHSA enrichment
  19. 2026-07-12 15:38 UTCGHSA enrichment
  20. 2026-07-12 02:59 UTCGHSA enrichment
  21. 2026-07-11 14:20 UTCGHSA enrichment
  22. 2026-07-11 08:27 UTCEPSS rescore
  23. 2026-07-11 01:41 UTCGHSA enrichment
  24. 2026-07-10 13:02 UTCGHSA enrichment
  25. 2026-07-10 00:23 UTCGHSA enrichment
Show 11 more
  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-09 11:45 UTCGHSA enrichment
  3. 2026-07-08 23:06 UTCGHSA enrichment
  4. 2026-07-08 15:15 UTCEPSS rescore
  5. 2026-07-08 15:15 UTCEPSS rescore
  6. 2026-07-08 10:26 UTCGHSA enrichment
  7. 2026-07-07 21:47 UTCGHSA enrichment
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-07 09:09 UTCGHSA enrichment
  10. 2026-07-06 20:30 UTCEG score recompute
  11. 2026-07-06 20:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-21379?
CVE-2026-21379 is a high vulnerability published on July 6, 2026. Memory Corruption when allocating memory with sizes that exceed the maximum allowed value.
When was CVE-2026-21379 disclosed?
CVE-2026-21379 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-21379 actively exploited?
CVE-2026-21379 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-21379?
CVE-2026-21379 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-21379?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21379, 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-21379

Explore →

Is Your Infrastructure Affected by CVE-2026-21379?

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

Start Free Scan →Browse All CVEs