What is CVE-2026-25262?

CVE-2026-25262 is Write-what-where Condition in Primary Bootloader. The supplied enrichment data classifies it as Unclassified mapped to CWE-123 CWE-123.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-25262. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-25262 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

9 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-25262 using CVSS 6.9, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumpublic exploit

CVE-2026-25262

CVE-2026-25262 — Write-what-where Condition in Primary Bootloader

Memory corruption while processing a crafted ELF file in the Primary Bootloader.

Published Sep 22, 2026Updated Sep 22, 2026Sources: NVD, Qualcomm, Inc. (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

Qualcomm, Inc.

8 products listed

CVSS base

6.9

medium

Remediation

The vendor's own words where we have them.

Upgrade Snapdragon to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Qualcomm, Inc.	Snapdragon	MDM9x07	Vulnerable
Qualcomm, Inc.	Snapdragon	MDM9x45	Vulnerable
Qualcomm, Inc.	Snapdragon	MDM9x55	Vulnerable
Qualcomm, Inc.	Snapdragon	MDM9x65	Vulnerable
Qualcomm, Inc.	Snapdragon	MSM8909	Vulnerable
Qualcomm, Inc.	Snapdragon	MSM8916	Vulnerable
Qualcomm, Inc.	Snapdragon	MSM8952	Vulnerable
Qualcomm, Inc.	Snapdragon	SDX50	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

High

Attack Vector

Physical

Privileges Req

Low

User Interaction

Required

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
6.9	CVSS 3.1	medium	0.3	6	NVD, Qualcomm, Inc. (CNA)

CVSS:3.1/AV:P/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-123 · Write-what-where Condition

Modify Memory
Execute Unauthorized Code or Commands
Gain Privileges or Assume Identity
DoS: Crash, Exit, or Restart

Mitigation: Use a language that provides appropriate memory abstractions.

Weakness & attack patterns

CWE-123

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

1 more posts on this CVEShowing 5 of 6 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Monitor for scanner or exploit-pattern traffic after 9 public PoC repositories were reported.

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 6.9 (AV:P)
Sep 22, 2026 · NVD
Initial · CVE published
Sep 22, 2026 · NVD
CVE published by MITRE.
Sep 22, 2026 · SOCRadar CTI
Cve is exploited therealfraudman/cve-2026-25262-msm8909-PoC
Aug 30, 2026 · SOCRadar CTI

Source activity

Readings a source repeats on a schedule, counted rather than listed.

6×SvrsMay 6, 2026 – Jul 23, 2026 · SOCRadar CTI
6×Tweets · 1 time tweeted.Apr 24, 2026 – Jul 1, 2026 · SOCRadar CTI
2×Github ReposJul 8, 2026 – Aug 30, 2026 · SOCRadar CTI
1×3 times mentioned on 2 Telegram channelsAug 20, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.May 6, 2026 · SOCRadar CTI

References

1 on the record

docs.qualcomm.com/product/publicresources/securitybulletin/may-2026-bulletin.html
Vendor Advisory

Coverage

8 stories from the feeds we poll

3 more reports on this CVEShowing 5 of 8 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Qualcomm, Inc.every CVE for this vendor
Unclassifiedsame class
CWE-123other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-25262 is Write-what-where Condition in Primary Bootloader, a medium vulnerability affecting Snapdragon from Qualcomm, Inc.. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-25262. Public exploit evidence is: 9 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.9 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.