CVE-2025-47331: Qualcomm Snapdragon · Buffer Over-read
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.07% 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:U/C:H/I:N/A:LExploitation 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. Monitor Qualcomm and device vendor advisories closely for firmware updates addressing CVE-2025-47331 and apply patches promptly. 2. Implement strict local access controls on devices using affected Snapdragon platforms to prevent unauthorized users from gaining low privilege access. 3. Employ endpoint detection and response (EDR) solutions to detect suspicious local activity that could indicate exploitation attempts. 4. For automotive and IoT deployments, enforce network segmentation and device authentication to limit attacker movement and access. 5. Conduct regular firmware inventory and vulnerability assessments to identify devices with vulnerable Qualcomm components. 6. Collaborate with device manufacturers to understand patch availability timelines and plan device update rollouts accordingly. 7. Educate users and administrators on the risks of local access vulnerabilities and enforce strong physical security controls. 8. Where feasible, consider deploying devices with alternative chipsets or architectures not affected by this vulnerability in high-risk environments.
Description
Information disclosure while processing a firmware event.