CVE-2026-25276 is a critical memory-corruption vulnerability in Qualcomm StrongBox Secure Processor firmware caused by improper validation of an array index. The flaw is described as a missing bounds check while using StrongBox, allowing an out-of-bounds memory access within the Secure Processing Unit implementation that underpins hardware-backed key management and related trust services on affected Qualcomm platforms. Because the vulnerable component operates inside the isolated secure processor environment used for cryptographic key generation, storage, attestation, signing, and encryption operations, exploitation can corrupt memory in a highly privileged trust boundary and potentially undermine StrongBox security guarantees.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical vulnerability in Qualcomm closed-source components addressed in Google's June 2026 Android security release.
A memory corruption vulnerability in Strongbox caused by a missing bounds check.
A related Qualcomm Secure Processor vulnerability involving improper validation of array index.
A critical vulnerability in Qualcomm Secure Processor mentioned as a companion vulnerability in the same June 2026 bulletin.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.