Skip to main content
CVE-2025-21421VulnerabilityPublished Updated

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

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% 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:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

AI-suggested

Until official patches are released by Qualcomm, organizations should implement strict local access controls to limit the ability of unprivileged users to interact with vulnerable APIs. Employing endpoint protection solutions that monitor for anomalous memory access patterns or suspicious API usage can help detect exploitation attempts. Device administrators should audit and restrict software installations and execution privileges to minimize the risk of local attackers gaining footholds. Network segmentation and device hardening can reduce exposure, especially in enterprise environments. Once Qualcomm releases patches or firmware updates, organizations must prioritize timely deployment across all affected devices. Additionally, monitoring vendor advisories and threat intelligence feeds for emerging exploit techniques related to this vulnerability is critical. For mobile devices, users should be encouraged to update their operating systems and firmware promptly. In environments where patching is delayed, consider disabling or restricting the vulnerable API if feasible. Finally, conducting regular security assessments and penetration tests focusing on local privilege escalation vectors can help identify and remediate exploitation paths related to this vulnerability.

Description

Memory corruption while processing escape code in API.

References

Community reviews

Loading reviews…