CVE-2026-25262 Write-What-Where in Qualcomm Sahara confirmed on Snapdragon 8 Gen 1 (SM8450) – partial Firehose auth bypass
Source Reddit Cybersecurity
Not known to be exploited · CVSS 6.9 Medium.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 20 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Qualcomm, Inc.Snapdragon | Affected
| Fixed in– |
AI-suggested
Researchers are actively investigating further steps to achieve full Firehose initialization and understand TrustZone dependencies. Until an official fix is released, no definitive mitigation can be recommended. Monitor vendor advisories for updates and patches addressing this vulnerability.
Discussion
CVE-2026-25262 is a write-what-where vulnerability in the Qualcomm Sahara protocol experimentally confirmed on the Snapdragon 8 Gen 1 (SM8450) platform. It allows arbitrary writes to SRAM during the Sahara handshake, bypassing signature verification and partially bypassing Firehose loader authorization. The loader executes and responds to commands without authorization errors, but full UFS storage access has not yet been achieved. The vulnerability was previously known only on legacy 32-bit Qualcomm platforms but now affects modern 64-bit ARMv9 SoCs. No official patch or remediation guidance is currently available, and research is ongoing to achieve full Firehose initialization and understand TrustZone dependencies.
r/cybersecurity (opens in a new tab)u/Asleep_Building_66690 points0 comments
I’d like to share the results of an experimental research note on the applicability of CVE-2026-25262 (Kaspersky ICS CERT, May 2026) to a modern 64-bit ARMv9 Qualcomm platform.
**Device:** POCO F4 GT (ingres) / Snapdragon 8 Gen 1 (SM8450, Waipio).
**What was done:**
- Static analysis of the engineering Firehose loader (`xbl_s_devprg_ns.melf`) in Ghidra identified the authorization state structure at `0x6B9CD500` (critical field `0x6B9CD538`).
- A modified Sahara client (`cve_final_single`, based on B. Kerler's edl) was created to exploit the CVE and deliver the loader to an arbitrary SRAM address (`0x2211C000`) *without* signature verification.
- An additional `SAHARA_CMD_RECV_DATA` packet injected the value `5` into the `is_authenticated` field before control was transferred to Firehose.
**Result (partial success):**
- Arbitrary write to SRAM via CVE-2026-25262 is **confirmed working** on SM8450.
- The loader executes and responds to commands (`nop` succeeds), no authorization error is observed.
- Full UFS access is **not yet achieved**; `getstorageinfo` and `read` return empty responses. Two hypotheses are being investigated: (1) loading only the LOAD segments without ELF/certificate overlay, and (2) potential TrustZone/SMC dependencies.
**Why this might be interesting:**
The official Qualcomm list for CVE-2026-25262 includes only 32-bit legacy platforms. This experiment suggests that the vulnerable code path in the Boot ROM is also present on the latest flagship SoCs, widening the scope of the vulnerability.
Full article, logs, PBL status codes, and static analysis notes are available in the repository:
https://github.com/shurikgo/cve-2026-25262-sm8450-research
No full exploit code is provided; the published material is sufficient for independent verification and further research.
*This work is shared for educational and research purposes only.*
Links cited in the discussion
Also discussed in r/ExploitDev