CVE-2026-21383

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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

Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.

CVSS v3
7.1
EG Score
7.1(high)
EPSS
0.0%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 8, 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-21383(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 5× in last 7d / 29× 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-18 10:04 UTCEPSS rescore
  2. 2026-07-18 10:04 UTCEPSS rescore
  3. 2026-07-16 23:00 UTCGHSA enrichment
  4. 2026-07-16 10:53 UTCGHSA enrichment
  5. 2026-07-15 22:46 UTCGHSA enrichment
  6. 2026-07-15 10:38 UTCGHSA enrichment
  7. 2026-07-14 22:28 UTCGHSA enrichment
  8. 2026-07-14 10:21 UTCGHSA enrichment
  9. 2026-07-13 22:14 UTCGHSA enrichment
  10. 2026-07-13 10:06 UTCGHSA enrichment
  11. 2026-07-12 21:57 UTCGHSA enrichment
  12. 2026-07-12 09:50 UTCGHSA enrichment
  13. 2026-07-11 21:43 UTCGHSA enrichment
  14. 2026-07-11 09:36 UTCGHSA enrichment
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-10 21:29 UTCGHSA enrichment
  17. 2026-07-10 09:21 UTCGHSA enrichment
  18. 2026-07-09 21:13 UTCGHSA enrichment
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 09:06 UTCGHSA enrichment
  21. 2026-07-08 20:59 UTCGHSA enrichment
  22. 2026-07-08 15:15 UTCEPSS rescore
  23. 2026-07-08 15:15 UTCEPSS rescore
  24. 2026-07-08 08:52 UTCGHSA enrichment
  25. 2026-07-07 20:45 UTCGHSA enrichment
Show 4 more
  1. 2026-07-07 13:46 UTCEPSS rescore
  2. 2026-07-07 08:38 UTCGHSA enrichment
  3. 2026-07-06 20:31 UTCEG score recompute
  4. 2026-07-06 20:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-21383?
CVE-2026-21383 is a high vulnerability published on July 6, 2026. Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
When was CVE-2026-21383 disclosed?
CVE-2026-21383 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21383 actively exploited?
CVE-2026-21383 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-21383?
CVE-2026-21383 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-21383?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21383, 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-21383

Explore →

Is Your Infrastructure Affected by CVE-2026-21383?

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

Start Free Scan →Browse All CVEs