CVE-2025-27055: Qualcomm Snapdragon · Buffer Over-read
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% 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 8 Jul 2025
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
AI-suggested
Organizations should prioritize the following mitigation steps: 1) Inventory and identify all devices and systems using affected Qualcomm Snapdragon platforms and components. 2) Monitor Qualcomm and device vendors for official patches or firmware updates addressing CVE-2025-27055 and apply them promptly once available. 3) Until patches are released, implement strict access controls to limit local access to affected devices, including enforcing least privilege principles and physical security measures. 4) Employ application whitelisting and endpoint detection and response (EDR) solutions to detect anomalous behavior indicative of exploitation attempts. 5) Restrict or monitor the processing of untrusted image data on affected devices, especially from external or removable media sources. 6) Conduct security awareness training to inform users about the risks of local exploitation and the importance of device security. 7) Collaborate with supply chain partners to ensure that devices are updated and secured against this vulnerability. These targeted actions go beyond generic advice by focusing on the specific nature of the vulnerability (local exploitation via image encoding) and the affected platforms.
Description
Memory corruption during the image encoding process.