Skip to main content

Qualcomm Snapdragon EUVDEUVD-2026-26992

| CVE-2026-25293 CRITICAL
Incorrect Authorization (CWE-863)
2026-05-04 qualcomm
9.6
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
9.6 CRITICAL
AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
Analysis Generated
May 04, 2026 - 17:48 vuln.today
EUVD ID Assigned
May 04, 2026 - 17:15 euvd
EUVD-2026-26992
Analysis Generated
May 04, 2026 - 17:15 vuln.today
CVE Published
May 04, 2026 - 16:43 nvd
CRITICAL 9.6

DescriptionCVE.org

Buffer overflow due to incorrect authorization in PLC FW

AnalysisAI

Buffer overflow in Qualcomm Snapdragon firmware enables authentication bypass on adjacent networks, allowing remote unauthenticated attackers to achieve complete system compromise with high impact to confidentiality, integrity, and availability. The vulnerability stems from incorrect authorization logic (CWE-863) that fails to prevent buffer overflow conditions. CVSS score of 9.6 reflects adjacent network attack vector with low complexity and no required privileges or user interaction, with scope change indicating container/hypervisor escape or lateral movement potential. No CISA KEV listing or public exploit identified at time of analysis, though EPSS data not available to assess exploitation probability.

Technical ContextAI

This vulnerability affects Qualcomm Snapdragon firmware, a system-on-chip (SoC) platform widely deployed in mobile devices, IoT endpoints, automotive systems, and embedded computing environments. The affected component is described as 'PLC FW' (likely programmable logic controller firmware or power line communication firmware within the SoC subsystem). The root cause is CWE-863 (Incorrect Authorization), indicating authorization checks fail to prevent a buffer overflow condition from being exploited. This combination suggests the authorization mechanism itself contains the buffer overflow, or authorization bypass enables subsequent buffer overflow exploitation. CPE identifier cpe:2.3:a:qualcomm,_inc.:snapdragon:*:*:*:*:*:*:*:* indicates broad Snapdragon product family impact, though specific affected models and firmware versions are not detailed in available CPE data. The vulnerability requires adjacent network access (AV:A), meaning attacker must be on the same network segment, subnet, or Bluetooth/Wi-Fi range rather than internet-routable.

RemediationAI

Apply firmware updates specified in the Qualcomm May 2026 Security Bulletin at https://docs.qualcomm.com/product/publicresources/securitybulletin/may-2026-bulletin.html, which should detail fixed firmware versions by Snapdragon model and provide OEM update guidance. For end-user devices (smartphones, tablets), monitor device manufacturer security bulletins and apply system updates as released, noting that OEM patch integration typically lags Qualcomm disclosure by weeks to months. For enterprise and embedded deployments, contact device vendors or system integrators for firmware update availability and deployment procedures. If patched firmware is not immediately available, implement network segmentation to isolate Snapdragon-based devices from untrusted adjacent networks - disable Wi-Fi Direct, Bluetooth discoverability, and ad-hoc networking features; enforce WPA3-Enterprise with 802.1X authentication for wireless networks; deploy VLANs to separate IoT/embedded devices from corporate networks; implement network access control (NAC) to restrict adjacent network access to authenticated, policy-compliant devices. These compensating controls reduce adjacent attack surface but add operational complexity for wireless-dependent use cases and may break Bluetooth/Wi-Fi Direct functionality required by some applications. For critical infrastructure or high-value targets, consider disabling affected PLC FW functionality entirely if operationally feasible, though specific feature identification requires vendor documentation.

CVE-2026-25289 CRITICAL
9.6 Aug 04

Memory corruption in Qualcomm Snapdragon Wi-Fi/NAN firmware allows an attacker within wireless range to overflow a stack

CVE-2026-25268 HIGH
8.8 Jul 06

Local privilege escalation and memory corruption in Qualcomm Snapdragon WLAN firmware occurs when the driver parses malf

CVE-2026-25277 HIGH
8.8 Jun 01

Memory corruption in Qualcomm Snapdragon Strongbox component allows local low-privileged attackers to trigger a buffer o

CVE-2026-25276 HIGH
8.8 Jun 01

Local privilege escalation in Qualcomm Snapdragon chipsets stems from an out-of-bounds memory access in the Strongbox tr

CVE-2025-47392 HIGH
8.8 Apr 06

Memory corruption in Qualcomm Snapdragon chipsets allows adjacent network attackers to achieve arbitrary code execution

CVE-2026-24088 HIGH
8.2 Jun 01

Bootloader integrity bypass in Qualcomm Snapdragon platforms allows a high-privileged local attacker to write to a speci

CVE-2026-24079 HIGH
8.1 Aug 04

Authentication bypass in Qualcomm Snapdragon SoCs allows adjacent network attackers to exploit a cryptographic flaw duri

CVE-2026-24083 HIGH
7.8 Aug 04

Memory corruption in Qualcomm Snapdragon IOCTL device driver handling enables a local low-privilege attacker to achieve

CVE-2026-24080 HIGH
7.8 Aug 04

Memory corruption in Qualcomm Snapdragon's fingerprint Trusted Application (TA) allows a local low-privileged attacker t

CVE-2026-21366 HIGH
7.8 Aug 04

Memory corruption in Qualcomm Snapdragon platforms occurs when a packet with a size value near the maximum allowable lim

CVE-2026-21379 HIGH
7.8 Jul 06

Local privilege escalation via memory corruption affects Qualcomm Snapdragon platforms, where allocating memory with siz

CVE-2025-59616 HIGH
7.8 Jul 06

Use-after-free memory corruption in Qualcomm Snapdragon platform driver code allows a local low-privileged process to tr

Share

EUVD-2026-26992 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy