Skip to main content
CVE-2025-21477VulnerabilityPublished

CVE-2025-21477: Qualcomm Snapdragon · Improper Input Validation

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

1. Immediate mitigation should focus on network-level protections: cellular network operators should implement strict validation and filtering of CCCH messages to prevent malformed data from reaching end devices. 2. Organizations should inventory and identify devices using affected Qualcomm Snapdragon components and monitor for unusual device reboots or connectivity interruptions. 3. Deploy network anomaly detection systems capable of identifying malformed signaling messages or unusual control channel traffic patterns. 4. Engage with device vendors and Qualcomm for timely firmware or software updates addressing this vulnerability once patches become available. 5. For critical deployments, consider fallback communication methods or redundant connectivity options to maintain availability during potential transient DoS events. 6. Educate IT and security teams about this vulnerability to enhance incident response readiness. 7. Where possible, apply configuration hardening on devices to limit exposure to untrusted networks or use VPNs and secure tunneling to reduce attack surface. 8. Collaborate with mobile network providers to ensure they are aware and actively mitigating risks associated with malformed CCCH data.

Description

Transient DOS while processing CCCH data when NW sends data with invalid length.

References

Community reviews

Loading reviews…