Skip to main content
CVE-2025-27034VulnerabilityPublished Updated

CVE-2025-27034: Qualcomm Snapdragon · Improper Validation of Array Index

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 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

1. Monitor Qualcomm advisories closely and apply official patches or firmware updates as soon as they become available for all affected Snapdragon platforms and associated modules. 2. For organizations deploying devices with affected chipsets, implement network segmentation and firewall rules to limit exposure of vulnerable devices to untrusted networks, especially restricting access to cellular modem interfaces where possible. 3. Employ intrusion detection and prevention systems (IDS/IPS) tuned to detect anomalous traffic patterns targeting cellular and wireless communication protocols. 4. Collaborate with device manufacturers and carriers to ensure timely rollout of security updates and validate patch deployment. 5. For critical environments, consider deploying endpoint protection solutions capable of detecting exploitation attempts or abnormal device behavior indicative of memory corruption exploits. 6. Educate users and administrators about the risk and encourage prompt installation of updates on mobile and IoT devices. 7. In the absence of immediate patches, temporarily disable or restrict features related to PLMN selection or SOR list handling if feasible, to reduce attack vectors.

Description

Memory corruption while selecting the PLMN from SOR failed list.

References

Community reviews

Loading reviews…