CVE-2025-21472: Qualcomm Snapdragon · Leftover Debug Code
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 09:15 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
To mitigate CVE-2025-21472, European organizations should: 1) Monitor vendor advisories closely and apply firmware or software updates from Qualcomm as soon as patches become available. 2) Restrict physical and local access to devices containing affected Qualcomm chipsets, especially in sensitive environments, to reduce the risk of local exploitation. 3) Implement strict device usage policies and endpoint security controls to detect and prevent unauthorized access or debugging attempts. 4) Conduct audits of device logs and debug settings to ensure that debug logging is disabled or properly secured in production devices. 5) For organizations developing products with affected chipsets, ensure that debug code is fully removed or disabled before deployment. 6) Employ encryption and secure key management practices to minimize the impact of any potential information leakage. 7) Educate users and administrators about the risks of local access vulnerabilities and encourage prompt reporting of suspicious device behavior. These steps go beyond generic advice by focusing on controlling local access, verifying debug configurations, and preparing for vendor patches.
Description
Information disclosure while capturing logs as eSE debug messages are logged.