Wrapped-key compromise via static AES-GCM initialization vector
Published Jul 6, 2026 · Updated Jul 6, 2026
Cryptographic weakness in Qualcomm Snapdragon HLOS allows local users to compromise wrapped-key confidentiality and integrity. The HLOS AES-GCM key-wrapping path supplies a static initialization vector, reusing the nonce-key pair instead of generating a unique value for every call. Low-privilege local access is required; successful exploitation exposes or alters cryptographic key material protected by the wrapper.
Summary
What happened
Cryptographic weakness in Qualcomm Snapdragon HLOS allows local users to compromise wrapped-key confidentiality and integrity. The HLOS AES-GCM key-wrapping path supplies a static initialization vector, reusing the nonce-key pair instead of generating a unique value for every call. Low-privilege local access is required; successful exploitation exposes or alters cryptographic key material protected by the wrapper.
The record
- CVE
- CVE-2026-21383
- Published
- Jul 6, 2026
- Updated
- Jul 6, 2026
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- CWE-323
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 6, 2026CVE publishedPublication date reported by the CVE source.
- Jul 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=FastConnect 6900
- Affected versionversion=FastConnect 7800
- Affected versionversion=LeMansAU
- Affected versionversion=LeMans_AU_LGIT
- Affected versionversion=Pandeiro
- Affected versionversion=QAM8255P
- Affected versionversion=QAM8397P
- Affected versionversion=QAM8797P
- Affected versionversion=QAMSRV1H
- Affected versionversion=QAMSRV1M
- Affected versionversion=QCA6595AU
- Affected versionversion=QCA6696
- Affected versionversion=QCA6698AQ
- Affected versionversion=QCA6797AQ
- Affected versionversion=QCA8695AU
- Affected versionversion=QDU1000
- Affected versionversion=QDU1110
- Affected versionversion=QDU1210
- Affected versionversion=QDX1010
- Affected versionversion=QDX1011
- Affected versionversion=QLN1083BD
- Affected versionversion=QLN1086BD
- Affected versionversion=QPA1083BD
- Affected versionversion=QPA1086BD
- Affected versionversion=Qualcomm Dragonwing X100 Accelerator Card
- Affected versionversion=QXM1093
- Affected versionversion=QXM1094
- Affected versionversion=QXM1095
- Affected versionversion=QXM1096
- Affected versionversion=SA7255P
- Affected versionversion=SA7775P
- Affected versionversion=SA8255P
- Affected versionversion=SA8620P
- Affected versionversion=SA8770P
- Affected versionversion=SA9000P
- Affected versionversion=SAR1165P
- Affected versionversion=SAR2130P
- Affected versionversion=Snapdragon AR1 Gen 1 Platform
- Affected versionversion=Snapdragon AR1+ Gen 1 Platform
- Affected versionversion=SRV1H
- Affected versionversion=SRV1M
- Affected versionversion=SXR2230P
- Affected versionversion=SXR2250P
- Affected versionversion=WCD9380
- Affected versionversion=WCD9385
- Affected versionversion=WCN3950
- Affected versionversion=WCN7860
- Affected versionversion=WCN7861
- Affected versionversion=WSA8830
- Affected versionversion=WSA8832
- Affected versionversion=WSA8835
- Affected versionversion=XRV7209
- Affected versionversion=XRV9209
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo