CVE-2025-59600: Qualcomm Snapdragon · Buffer Over-read
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 29 Oct 2026, 19:04 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 2 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Qualcomm, Inc.Snapdragon | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-59600, organizations and device manufacturers should: 1) Monitor Qualcomm advisories closely and apply official patches or firmware updates as soon as they become available. 2) Implement strict input validation and bounds checking in software components interacting with user-supplied data to prevent buffer over-read conditions. 3) Employ runtime protections such as Address Space Layout Randomization (ASLR), Data Execution Prevention (DEP), and Control Flow Integrity (CFI) to reduce exploitation success. 4) Restrict local access to devices by enforcing strong authentication and limiting privilege escalation vectors. 5) Conduct thorough security testing and code audits on custom firmware or software layers built on affected Snapdragon platforms. 6) For enterprise environments, deploy endpoint detection and response (EDR) solutions to identify anomalous behaviors indicative of exploitation attempts. 7) Educate users on the risks of installing untrusted applications that could provide local attack vectors. 8) Consider network segmentation and device isolation strategies for IoT and wearable devices to contain potential breaches. These steps, combined with timely patching, will significantly reduce the risk posed by this vulnerability.
Description
Memory Corruption when adding user-supplied data without checking available buffer space.