Skip to main content
CVE-2025-21449VulnerabilityPublished

CVE-2025-21449: Qualcomm Snapdragon · Buffer Over-read

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 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 15% 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 8 Jul 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-25.

What to do

AI-suggested

To mitigate CVE-2025-21449 effectively, European organizations should: 1) Monitor Qualcomm’s official advisories and promptly apply firmware and software updates once patches become available, as no patches are currently linked. 2) Implement network-level filtering to detect and block malformed SSID IEs or suspicious Wi-Fi management frames using advanced intrusion detection/prevention systems (IDS/IPS) capable of deep packet inspection for wireless protocols. 3) Segment wireless networks to isolate critical devices and reduce exposure to potentially malicious Wi-Fi traffic, limiting the attack surface. 4) Employ device management solutions to inventory and track all Qualcomm Snapdragon-based devices, ensuring rapid identification and remediation of vulnerable endpoints. 5) For automotive and industrial deployments, coordinate with vendors to schedule maintenance windows for firmware updates and consider fallback communication methods to maintain operational continuity during remediation. 6) Educate IT and security teams about the nature of the vulnerability to recognize symptoms of transient DoS and respond quickly to device outages. 7) Where feasible, disable or limit Wi-Fi scanning or connectivity features on devices that do not require them, reducing exposure to malformed SSID IE attacks. These measures go beyond generic patching advice by emphasizing network-level controls, asset management, and operational continuity planning tailored to the diverse environments where Snapdragon platforms are deployed.

Description

Transient DOS may occur while processing malformed length field in SSID IEs.

References

Community reviews

Loading reviews…