Skip to main content
Mallory
HighVulnerability

CVE-2026-50658: Local Privilege Escalation in Microsoft Defender for Endpoint for Mac

Published Jul 14, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS7.0High · v3.1
EPSS0.20%10th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-50658CWE-367 · Time-of-check Time-of-use (TOCTOU)…

CVE-2026-50658 is a time-of-check/time-of-use race condition in Microsoft Defender for Endpoint for Mac that enables local privilege escalation. The root-privileged Defender daemon validates IPC callers using a PID captured at connection time and an executable path retrieved later. A local attacker can queue a request and execute an allowlisted, Microsoft-signed Defender binary before validation, bypassing the private socket's caller-identity check. The handle_threat restore operation (opcode 0x05) also skips administrative authorization when its optional authorization structure is omitted. Combining these weaknesses allows attacker-controlled quarantine contents to be restored as new files in privileged locations. The restore operation refuses to overwrite existing files.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A local attacker can create files containing attacker-controlled data in privileged locations and escalate to root. A demonstrated exploit used the file-creation primitive to introduce a system-wide cron configuration, causing an attacker-supplied command to execute as root within approximately one minute. The primitive does not permit unrestricted overwriting of existing files.

Mitigation

If you can’t patch tonight, do this now.

No vendor-provided workaround is specified. Implementation-level defenses include audit-token-based IPC identity validation or macOS-native XPC peer-signing controls, together with mandatory administrative authorization for quarantine restoration, including when an authorization structure is omitted. These hardening measures do not replace installing the security update.

Remediation

Patch, then assume compromise.

Apply Microsoft's July 2026 security update for Microsoft Defender for Endpoint for Mac addressing CVE-2026-50658, associated with the July 14, 2026 release. Specific affected and fixed product version numbers are not available.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationMicrosoft Defender For Endpointapplication
FAQ

Frequently asked questions

Is CVE-2026-50658 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-50658 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-50658?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-50658.
Is there a patch for CVE-2026-50658?
Apply Microsoft's July 2026 security update for Microsoft Defender for Endpoint for Mac addressing CVE-2026-50658, associated with the July 14, 2026 release. Specific affected and fixed product version numbers are not available.
What products are affected by CVE-2026-50658?
Microsoft Corporation Microsoft Defender For Endpoint.
How severe is CVE-2026-50658?
CVE-2026-50658 has a CVSS v3.1 score of 7.0 (High) and an EPSS score of 0.20% (10th percentile) as of Nov 17, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.