CVE-2025-47345: Qualcomm Snapdragon · Reusing a Nonce, Key Pair in Encryption
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 8.4 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Qualcomm, Inc.Snapdragon | Affected
| Fixed in– |
AI-suggested
1. Immediate coordination with device manufacturers and Qualcomm to obtain and deploy official patches that address nonce reuse in encryption routines. 2. For organizations managing fleets of devices, implement asset inventory and identify all devices with affected Snapdragon components to prioritize patching. 3. Employ endpoint detection and response (EDR) tools to monitor for unusual local access patterns or attempts to access cryptographic license data. 4. Where possible, enforce strict access controls and limit local user privileges to reduce the attack surface. 5. Conduct cryptographic audits on custom applications interfacing with affected hardware to ensure nonce uniqueness and proper key management. 6. For automotive and IoT deployments, apply network segmentation and anomaly detection to detect exploitation attempts. 7. Maintain up-to-date threat intelligence feeds to monitor for emerging exploits targeting this vulnerability. 8. Educate internal security teams about the vulnerability’s specifics to enhance incident response readiness. 9. Consider temporary compensating controls such as disabling non-essential local interfaces that could be leveraged for exploitation until patches are applied. 10. Engage with Qualcomm and industry groups for coordinated vulnerability disclosure and mitigation guidance.
Description
Cryptographic issue may occur while encrypting license data.