Skip to main content
CVE-2025-21450VulnerabilityPublished

CVE-2025-21450: Qualcomm Snapdragon · Improper Authentication

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% 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: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 2026-10-25.

What to do

AI-suggested

Immediate mitigation steps include: 1) Inventory and identify all devices and systems using affected Qualcomm Snapdragon platforms and wireless components within the organization. 2) Monitor Qualcomm’s official security advisories and vendor communications for patches or firmware updates addressing CVE-2025-21450. 3) Where possible, apply network segmentation and strict access controls to limit exposure of vulnerable devices to untrusted networks. 4) Employ network-level protections such as intrusion detection/prevention systems (IDS/IPS) configured to detect anomalous download or connection behaviors associated with this vulnerability. 5) For critical systems, consider deploying endpoint detection and response (EDR) solutions capable of identifying unusual activities related to firmware or software downloads. 6) Engage with device manufacturers and service providers to ensure timely updates and support. 7) Educate IT and security teams about the nature of this vulnerability to enhance monitoring and incident response readiness. 8) As a longer-term measure, evaluate the security posture of devices relying on affected components and consider alternative hardware or software solutions if patches are delayed or unavailable.

Description

Cryptographic issue occurs due to use of insecure connection method while downloading.

References

Community reviews

Loading reviews…