CVE-2025-47326VulnerabilityPublished 24 Sep 2025Updated 25 Sep 2025

CVE-2025-47326: 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 14% 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 24 Sep 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

To mitigate the risk posed by CVE-2025-47326, European organizations should take a multi-layered approach: 1) Inventory and identify all devices and infrastructure components using affected Qualcomm Snapdragon chipsets, including mobile devices, routers, gateways, and embedded systems. 2) Engage with device manufacturers and vendors to obtain firmware or software updates addressing this vulnerability as soon as patches become available. Given the lack of patch links currently, maintain close monitoring of vendor advisories and Qualcomm security bulletins. 3) Implement network segmentation and access controls to limit exposure of vulnerable devices to untrusted networks, reducing the attack surface. 4) Employ intrusion detection and prevention systems (IDS/IPS) with updated signatures to detect anomalous traffic patterns that may exploit this vulnerability. 5) For critical systems, consider temporary workarounds such as disabling non-essential wireless interfaces or power control features if feasible and supported by vendors. 6) Maintain robust incident response plans to quickly identify and remediate any service disruptions potentially caused by exploitation attempts. 7) Educate IT and security teams about the vulnerability’s nature and signs of exploitation to enhance detection capabilities. 8) Monitor threat intelligence feeds for any emerging exploit code or attack campaigns targeting this vulnerability to adjust defenses promptly.

Description

Transient DOS while handling command data during power control processing.

Impact

For European organizations, the impact of CVE-2025-47326 can be significant, particularly for those relying on networking infrastructure, mobile communications, and IoT devices powered by Qualcomm Snapdragon chipsets. The transient DoS condition could disrupt critical communications, degrade network availability, and cause service interruptions. Telecommunications providers, enterprises with large mobile device fleets, and industries deploying IoT solutions (e.g., smart buildings, manufacturing, healthcare) may experience operational disruptions. The vulnerability’s network-based attack vector means that attackers can potentially exploit it remotely without authentication or user interaction, increasing the risk of widespread impact. Although the vulnerability does not compromise data confidentiality or integrity, the availability impact alone can lead to downtime, loss of productivity, and potential cascading failures in dependent systems. In sectors such as finance, healthcare, and critical infrastructure, even transient outages can have severe consequences. Additionally, the broad range of affected Qualcomm products means that patching and mitigation efforts may be complex and require coordination with multiple vendors and device manufacturers. The absence of known exploits in the wild currently reduces immediate risk but does not preclude future exploitation attempts, especially as threat actors analyze the vulnerability details post-disclosure.

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 2 Oct 2025, 01:00 UTC

WeaknessesCWE-126

Technical details

References

Community reviews

Related threats