Security readout for executives and security teams
Plain-English summary
A flaw in WLAN firmware can corrupt memory when an affected Qualcomm platform processes a malformed nearby-device discovery frame. No user action or authentication is required. Successful exploitation could compromise confidentiality, integrity, and availability, but the supplied sources do not confirm real-world exploitation.
Executive priority
Treat as an urgent exposure-identification and vendor-patching issue because compromise requires neither credentials nor user action and may have broad impact. Prioritize confirmed affected assets near untrusted users or wireless environments. Do not represent exploitation as active based on the supplied evidence.
Technical view
CVE-2026-25289 is a stack-based buffer overflow (CWE-121) triggered by invalid length values in Device Capability Extended attributes within certain NAN Service Discovery Frames. It is rated CVSS 9.6 because an adjacent, unauthenticated attacker may achieve high-impact compromise without user interaction, potentially crossing security boundaries.
Likely exposure
Exposure is limited to devices containing one of the explicitly listed affected Qualcomm Snapdragon, FastConnect, QCA, QCN, WCN, IPQ, automotive, networking, mobile, XR, or related platforms. Product branding alone is insufficient; organizations must confirm the embedded chipset and firmware through OEM documentation or asset records.
Exploitation context
The CVSS vector indicates an attacker must be adjacent, such as within relevant wireless range. Attack complexity is low, with no privileges or user interaction required. The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
The vulnerable parser handles Device Capability Extended attributes in certain NAN Service Discovery Frames with invalid lengths. The record identifies memory corruption and CWE-121 but does not establish the precise affected firmware versions, exploit reliability, mitigations, or patched builds. Testing should remain authorized and non-disruptive because malformed wireless frames may crash devices.
Mitigation direction
- Review Qualcomm's August 2026 bulletin for the official remediation and affected firmware details.
- Request applicable firmware or system updates from each device manufacturer or carrier.
- Prioritize nearby-discovery-capable devices in sensitive, public, or untrusted wireless environments.
- Apply vendor-recommended feature restrictions or compensating controls if updates are unavailable.
Validation and detection
- Inventory devices containing the specifically listed Qualcomm platforms, including embedded and networking equipment.
- Record chipset, WLAN firmware, operating-system build, OEM, and carrier for each potentially affected asset.
- Compare installed firmware against Qualcomm and OEM remediation guidance.
- Verify updates through device management telemetry or authenticated firmware version reporting.
- Monitor vendor advisories because the supplied sources do not specify fixed versions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-25289 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H2.86qualcommVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://docs.qualcomm.com/product/publicresources/securitybulletin/august-2026-bulletin.htmlCVE reference, qualcomm
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.