CVE-2025-47330: Qualcomm Snapdragon · Buffer Over-read
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 08:30 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:N/I:N/A:HExploitation 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Qualcomm, Inc.Snapdragon | Affected
| Fixed in– |
AI-suggested
1. Monitor Qualcomm and device manufacturers for official patches or firmware updates addressing CVE-2025-47330 and apply them promptly once available. 2. Restrict local access to video firmware interfaces and related system components to trusted users and processes only, minimizing the risk of local exploitation. 3. Implement strict endpoint security controls to prevent unauthorized local access, including strong authentication, privilege management, and endpoint detection and response (EDR) solutions. 4. For enterprise-managed devices, enforce mobile device management (MDM) policies that limit installation of untrusted applications and control firmware updates. 5. Conduct regular security audits and vulnerability assessments on devices with Qualcomm Snapdragon chipsets to identify potential exploitation attempts. 6. Educate users and administrators about the risks of local privilege escalation and the importance of maintaining updated device firmware. 7. In automotive or IoT deployments, ensure secure firmware update mechanisms and network segmentation to isolate vulnerable components. 8. Consider deploying runtime protections or sandboxing for video processing components if supported by the platform. These steps go beyond generic advice by focusing on access control to the vulnerable component, proactive patch management, and environment hardening specific to Qualcomm Snapdragon-based devices.
Description
Transient DOS while parsing video packets received from the video firmware.