CVE-2025-27065VulnerabilityPublished 6 Aug 2025

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

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 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

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 vendors for official patches or firmware updates addressing CVE-2025-27065 and apply them promptly once available. 2. Implement network-level filtering to detect and block malformed frames or suspicious wireless traffic patterns that could trigger the vulnerability, using advanced intrusion detection/prevention systems (IDS/IPS) tailored for wireless protocols. 3. For enterprise-managed mobile devices, enforce strict network access controls and use Mobile Device Management (MDM) solutions to ensure devices are updated and monitored for anomalous behavior. 4. Segment critical wireless networks to limit exposure and reduce the attack surface, isolating vulnerable devices from sensitive systems. 5. Conduct regular wireless network audits and vulnerability assessments to identify devices with affected Qualcomm chipsets and prioritize remediation. 6. In automotive or IoT deployments, coordinate with hardware vendors to schedule firmware updates and consider fallback mechanisms to maintain availability during patching. 7. Educate security teams on monitoring for transient DoS symptoms related to wireless connectivity issues that may indicate exploitation attempts. These targeted measures go beyond generic advice by focusing on network traffic filtering, device management, and segmentation specific to the affected Qualcomm wireless components.

Description

Transient DOS while processing a frame with malformed shared-key descriptor.

Impact

For European organizations, the impact of CVE-2025-27065 can be significant due to the widespread use of Qualcomm Snapdragon chipsets in mobile devices, IoT endpoints, and networking hardware. Enterprises relying on mobile communications, remote IoT sensors, or wireless infrastructure that incorporate affected Qualcomm components may experience service disruptions or degraded availability if targeted. The transient DoS could interrupt critical communications, affecting business operations, especially in sectors like telecommunications, finance, healthcare, and manufacturing where wireless connectivity is essential. Additionally, automotive systems using Snapdragon platforms for telematics or infotainment could face temporary outages, potentially impacting safety or user experience. Although the vulnerability does not compromise confidentiality or integrity, the availability impact can lead to operational downtime, increased support costs, and potential reputational damage. The lack of required privileges or user interaction means attackers can attempt exploitation remotely over the network, increasing the risk surface. However, the absence of known exploits in the wild currently reduces immediate threat levels, but proactive mitigation is advised given the broad device footprint.

CWE-126Buffer Over-read (opens in a new tab)
Variant weakness
The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
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-126

Technical details

References

Community reviews

Related threats