CVE-2025-27045VulnerabilityPublished 9 Oct 2025

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

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Oct 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 26 Oct 2026.

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

To mitigate CVE-2025-27045, European organizations should implement several targeted measures beyond generic patching advice. First, restrict local access to devices with affected Qualcomm Snapdragon chipsets by enforcing strict endpoint security policies, including application whitelisting and privilege management to prevent unauthorized code execution. Monitor device logs and behavior for anomalies indicative of exploitation attempts, such as unusual memory access patterns or batch command executions. Employ mobile device management (MDM) solutions to enforce security configurations and promptly deploy vendor patches once available. For IoT deployments, segment networks to isolate vulnerable devices and limit exposure. Additionally, conduct regular security audits and penetration testing focusing on local privilege escalation and memory disclosure vectors. Engage with Qualcomm and device manufacturers to obtain timely firmware updates and validate patch effectiveness. Educate users and administrators about the risks of local exploitation and the importance of maintaining device hygiene. Finally, consider deploying runtime memory protection technologies where feasible to detect and prevent buffer over-read attempts.

Description

CVE-2025-27045 is a medium severity buffer over-read vulnerability in Qualcomm Snapdragon devices affecting multiple FastConnect and other chipsets. It arises from improper handling of batch command execution in the video driver, leading to potential information disclosure. The vulnerability requires local access with low privileges and no user interaction. Exploitation could allow attackers to read sensitive memory contents, impacting confidentiality but not integrity or availability. No known exploits are currently reported in the wild. European organizations using affected Snapdragon-based devices, especially in mobile and IoT sectors, should prioritize patching once available. Mitigations include restricting local access, monitoring for unusual device behavior, and applying vendor updates promptly. Countries with high adoption of Qualcomm Snapdragon devices and strong mobile ecosystems, such as Germany, France, and the UK, are most likely to be impacted. Given the medium CVSS score and attack complexity, the threat is moderate but warrants attention due to potential data leakage risks.

Impact

For European organizations, the primary impact of CVE-2025-27045 is the potential leakage of sensitive information from devices running affected Qualcomm Snapdragon chipsets. This could include corporate mobile devices, IoT endpoints, and embedded systems used in critical infrastructure or enterprise environments. Confidentiality breaches could lead to exposure of proprietary data, credentials, or cryptographic material, increasing the risk of further attacks such as lateral movement or privilege escalation. Although the vulnerability does not affect system integrity or availability, the information disclosure could undermine trust and compliance with data protection regulations like GDPR. The local attack vector limits remote exploitation, but insider threats or malware with local access could exploit this flaw. The impact is particularly significant for sectors relying heavily on mobile and wireless technologies, including telecommunications, manufacturing, and government agencies. Failure to address this vulnerability could result in targeted espionage or data theft campaigns within European markets.

Summary

CVE-2025-27045 is a buffer over-read vulnerability classified under CWE-126, discovered in the video driver component of Qualcomm Snapdragon chipsets, including FastConnect 6900, 7800, and various other models like QCC2072 and WCD series. The flaw occurs during the processing of batch command execution, where the driver improperly handles memory boundaries, allowing an attacker with local low-privilege access to read beyond intended memory buffers. This results in information disclosure, potentially leaking sensitive data stored in memory. The vulnerability does not require user interaction and has a CVSS 3.1 base score of 6.1, indicating medium severity. The attack vector is local, with low complexity and privileges required, but no integrity or availability impact is noted. No public exploits have been reported yet, and Qualcomm has not released patches at the time of publication. The vulnerability affects a broad range of Snapdragon-based devices, commonly used in smartphones, IoT devices, and wireless communication modules, making it relevant for a wide user base. The flaw's exploitation could be leveraged by attackers who have gained local access, such as through compromised applications or insider threats, to extract confidential information from device memory.

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/october-2025-bulletin.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 16 Oct 2025, 08:55 UTC

WeaknessesCWE-126

Technical details

References

Community reviews

Related threats