CVE-2025-27066VulnerabilityPublished 6 Aug 2025

CVE-2025-27066: Qualcomm Snapdragon · Reachable Assertion

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 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 20% 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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Monitor Qualcomm and device vendor advisories closely for patches or firmware updates addressing CVE-2025-27066 and apply them promptly once available. 2. Implement network-level filtering to block or scrutinize ANQP messages from untrusted or external sources, especially on Wi-Fi networks, to reduce exposure to malicious crafted ANQP packets. 3. For enterprise-managed mobile devices, enforce mobile device management (MDM) policies to ensure devices are updated regularly and restrict connectivity to trusted networks. 4. In automotive and IoT deployments, segment networks to isolate vulnerable devices and limit exposure to untrusted wireless traffic. 5. Employ anomaly detection systems to identify unusual network traffic patterns that could indicate attempts to exploit this vulnerability. 6. Engage with device manufacturers and suppliers to confirm the presence of this vulnerability in deployed hardware and request mitigation guidance or updates. 7. Prepare incident response plans to handle transient denial of service events affecting critical wireless communication systems. 8. Where possible, disable or restrict ANQP processing on devices or access points if not required for network operations.

Description

Transient DOS while processing an ANQP message.

Impact

For European organizations, the impact of CVE-2025-27066 could be significant, especially for those relying on devices and infrastructure powered by Qualcomm Snapdragon chipsets. The transient denial of service could disrupt mobile communications, IoT device operations, automotive systems, and wireless connectivity. This could affect enterprise mobile users, critical infrastructure relying on IoT sensors and devices, automotive fleets using Snapdragon-based telematics, and consumer devices used within corporate environments. Disruptions in wireless connectivity could degrade productivity, cause loss of real-time data, and impact safety-critical systems in automotive or industrial contexts. Although the vulnerability does not compromise confidentiality or integrity, the availability impact could lead to operational downtime and service interruptions. The broad range of affected products means that many sectors including telecommunications, manufacturing, automotive, healthcare, and public services could be impacted. The lack of known exploits currently reduces immediate risk, but the ease of exploitation (no privileges or user interaction needed) means attackers could develop exploits quickly once the vulnerability is publicly known. European organizations with large deployments of Qualcomm-based devices should consider this a high-priority issue.

CWE-617Reachable Assertion (opens in a new tab)
Base weakness
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Implementation
Make sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)
Implementation · Input Validation
Perform input validation on user data.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

docs.qualcomm.com/product/publicresources/securitybulletin/august-2025-bulletin.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 6 Aug 2025, 08:04 UTC

WeaknessesCWE-617

Technical details

References

Community reviews

Related threats