CVE-2025-47343: Qualcomm Snapdragon · Untrusted Pointer Dereference
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 07:57 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:U/C:H/I:H/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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Qualcomm, Inc.Snapdragon | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-47343, European organizations should implement a multi-layered approach: 1) Monitor Qualcomm and device vendors for official patches or firmware updates addressing this vulnerability and deploy them promptly across all affected devices. 2) Restrict local access to devices, especially limiting access to video processing interfaces and services that handle video session parameters, through device hardening and access control policies. 3) Employ endpoint detection and response (EDR) solutions capable of identifying anomalous behavior related to memory corruption or unauthorized video session manipulations. 4) Enforce strict privilege management to minimize the number of users and processes with the ability to interact with vulnerable components. 5) Conduct regular security audits and vulnerability assessments on mobile and embedded devices within the organization’s infrastructure. 6) Educate users and administrators about the risks of local privilege escalation and the importance of device security hygiene. 7) Consider network segmentation to isolate critical systems from devices that might be compromised via this vulnerability. 8) Collaborate with device manufacturers and service providers to ensure timely communication and coordinated response to emerging threats related to this vulnerability.
Description
Memory corruption while processing a video session to set video parameters.