Loading vulnerability…
CVE-2025-26403 is an out-of-bounds write vulnerability in the memory subsystem of some Intel Xeon 6 processors. According to the provided content, the flaw is present when Intel Software Guard Extensions (SGX) or Intel Trust Domain Extensions (TDX) is enabled and in use. The issue is attributed to insufficient bounds checking in memory operations associated with the SGX/TDX implementation, allowing writes beyond intended memory boundaries. Intel states that exploitation may allow a privileged local user to potentially enable escalation of privilege. The issue affects Intel Xeon 6 processors on the Birch Stream server platform, including listed P-core and E-core variants, and is addressed through Intel-released microcode updates distributed via system firmware updates from OEMs.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An out-of-bounds write vulnerability in the memory subsystem of some Intel Xeon 6 processors when using Intel SGX or Intel TDX that may allow local privilege escalation by a privileged user.
An out-of-bounds write vulnerability in the memory subsystem of Intel Xeon 6 processors that can allow a local privileged user to corrupt memory and potentially escalate privileges when SGX or TDX is enabled and in use.
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.