CVE-2025-21427VulnerabilityPublished 8 Jul 2025

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

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 8.2 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.2High

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:H/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
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: 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: 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 8 Jul 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

Given the lack of currently available patches, European organizations should implement the following specific mitigations: 1) Inventory and identify all devices using affected Qualcomm Snapdragon platforms, including mobile devices, embedded systems, and automotive components. 2) Prioritize firmware and software updates from device manufacturers and Qualcomm as soon as patches become available, ensuring rapid deployment especially in critical systems. 3) Employ network-level RTP traffic inspection and filtering to detect and block malformed or suspicious RTP packets that could trigger the vulnerability. 4) Use endpoint security solutions capable of monitoring anomalous RTP decoding behavior or memory access violations on affected devices. 5) For enterprise VoIP and video conferencing infrastructure, consider isolating RTP streams within secure, segmented networks to reduce exposure. 6) Educate users about the risks of connecting to untrusted networks where malicious RTP packets could be injected. 7) Collaborate with vendors to obtain timely security advisories and firmware updates. 8) For automotive and IoT deployments, implement network segmentation and strict access controls to limit exposure of vulnerable devices to external networks. These measures go beyond generic advice by focusing on proactive device identification, network traffic controls, and vendor coordination tailored to the specific nature of this RTP decoding vulnerability.

Description

Information disclosure while decoding this RTP packet Payload when UE receives the RTP packet from the network.

Impact

For European organizations, the impact of CVE-2025-21427 is substantial due to the widespread use of Qualcomm Snapdragon chipsets in smartphones, tablets, automotive infotainment systems, and IoT devices across the continent. Information disclosure through this vulnerability could lead to leakage of sensitive communication data, including voice and video streams, potentially exposing confidential business conversations, personal data, or proprietary information. This could undermine privacy compliance obligations under GDPR and other data protection regulations. Additionally, sectors such as automotive, healthcare, and critical infrastructure that utilize Snapdragon-based embedded platforms for communication may face risks of espionage or targeted data leaks. The vulnerability's remote exploitability without user interaction increases the threat surface, especially in environments with high network exposure or where RTP streams are common, such as VoIP services, video conferencing, and real-time collaboration tools. Although no integrity or availability impacts are noted, the confidentiality breach alone can have severe reputational and regulatory consequences for European enterprises and public sector entities.

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Jul 2025, 13:15 UTC

WeaknessesCWE-126

Technical details

References

Community reviews

Related threats