Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
CVE-2026-21383
HIGHPre-NVD 7.17.1—Trending — 3 sources updated this week
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: 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: —CVSS: 7.1Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EPSS
- —
- KEV
- Not listed
Published
July 6, 2026
Last Modified
July 6, 2026
References (1)
- product-security@qualcommhttps://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 4× in last 7d / 4× 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.
- 2026-07-07 08:39 UTCEG score recompute
- 2026-07-07 08:38 UTCGHSA enrichment
- 2026-07-06 20:31 UTCEG score recompute
- 2026-07-06 20:29 UTCMITRE cvelistV5first tracked
Frequently asked(4)
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. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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
Is Your Infrastructure Affected by CVE-2026-21383?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.