Skip to main content
VulnerabilityPublished Updated

CVE-2025-21422: Qualcomm Snapdragon · Cryptographic Issues

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% 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:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 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 26 Oct 2026.

What to do

AI-suggested

1. Monitor Qualcomm advisories and apply official patches or firmware updates as soon as they are released to address this vulnerability. 2. Until patches are available, restrict local access to affected devices by enforcing strict access controls and minimizing privileged user accounts. 3. Implement additional cryptographic hygiene by ensuring that cryptographic keys and IVs are managed and generated securely at the application level where possible, including using hardware-backed key stores and avoiding reuse of cryptographic parameters. 4. Conduct thorough security audits of cryptographic implementations in software running on affected platforms to detect potential misuse or weaknesses. 5. Employ runtime integrity monitoring and anomaly detection to identify suspicious cryptographic operations that may indicate exploitation attempts. 6. For enterprise deployments, consider network segmentation and device isolation to limit the impact of a compromised device. 7. Educate users and administrators about the risks of local privilege escalation and the importance of timely updates. 8. Collaborate with vendors and security teams to develop incident response plans specific to cryptographic vulnerabilities on Snapdragon devices.

Description

Cryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses.

References

Community reviews

Loading reviews…