CVE-2025-27072: Qualcomm Snapdragon · Classic Buffer Overflow
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 11:07 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:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Aug 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 26 Oct 2026.
What to do
AI-suggested
Given the local access requirement, European organizations should focus on strengthening physical and local network security controls to prevent unauthorized access to vulnerable devices. Specific mitigation steps include: 1) Inventory and identify all devices using affected Qualcomm Snapdragon chipsets within the organization’s environment. 2) Monitor vendor communications closely for official patches or firmware updates addressing CVE-2025-27072 and apply them promptly once available. 3) Implement strict access controls and device hardening to limit local user privileges and prevent unauthorized device manipulation. 4) Employ network segmentation to isolate critical devices and reduce the attack surface for local exploits. 5) Use endpoint detection and response (EDR) tools to monitor for unusual local activity that could indicate exploitation attempts. 6) Educate users and administrators about the risks of local access vulnerabilities and enforce policies to prevent unauthorized physical access to devices. 7) For embedded and IoT devices, consider deploying runtime protections such as memory safety enforcement or anomaly detection to mitigate buffer overflow exploitation. 8) Collaborate with device manufacturers and suppliers to ensure timely vulnerability management and secure device lifecycle practices.
Description
Information disclosure while processing a packet at EAVB BE side with invalid header length.