Skip to main content
VulnerabilityPublished

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

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 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 26 Oct 2026.

What to do

AI-suggested

  1. Immediate mitigation should focus on network-level controls to filter and monitor beacon frames with anomalous or malformed IE header lengths. Deploy advanced wireless intrusion detection/prevention systems (WIDS/WIPS) capable of identifying and blocking suspicious beacon frames.
  2. Coordinate with device and equipment vendors to obtain and apply firmware or software updates as soon as patches become available. Qualcomm and OEMs should prioritize releasing fixes for affected platforms.
  3. Implement network segmentation to isolate critical wireless infrastructure from untrusted or public wireless networks, reducing exposure to malicious beacon frames.
  4. Employ robust monitoring and logging of wireless network traffic to detect unusual patterns indicative of exploitation attempts.
  5. For enterprise mobile devices, enforce strict device management policies including disabling unnecessary wireless interfaces when not in use and restricting connections to trusted networks.
  6. Engage with telecom providers to ensure that base stations and network equipment using affected Qualcomm chipsets are updated and hardened against such attacks.
  7. Educate security teams to recognize symptoms of transient DoS conditions related to wireless connectivity and establish incident response procedures tailored to this vulnerability.

Description

Transient DOS while handling beacon frames with invalid IE header length.

References

Community reviews

Loading reviews…