Affects Microsoft Windows Runtime (core OS component) widely deployed across enterprises; local privilege escalation can enable full system/domain compromise if chained.
CVE-2026-50413
Use-after-free in Windows Runtime allows local privilege escalation on Windows.
Is CVE-2026-50413 being exploited?
Not confirmed. CVE-2026-50413 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-50413?
CVE-2026-50413 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-50413?
Yes. A fix has been recorded for CVE-2026-50413. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-50413 affect?
CVE-2026-50413 affects Microsoft Windows Runtime (WinRT) / Windows OS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-50413?
Apply vendor updates when released; restrict local admin rights; monitor for privilege escalation events.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local authenticated attacker can escalate to SYSTEM/root, enabling persistence, access to sensitive data, and execution of privileged actions.
Patch when possible
- affected>= 10.0.26100.0 and < 10.0.26100.8875
- affected>= 10.0.26200.0 and < 10.0.26200.8875
- affected>= 10.0.28000.0 and < 10.0.28000.2525
- affected>= 10.0.26100.0 and < 10.0.26100.33158
- affected>= 10.0.26100.0 and < 10.0.26100.33158
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.