Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2025-29969: Remote Code Execution in Windows MS-EVEN EventLog RPC

Published May 13, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS1.2%69th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2025-29969CWE-367 · Time-of-check Time-of-use (TOCTOU)…

CVE-2025-29969 is a time-of-check time-of-use race condition in Microsoft Windows affecting the MS-EVEN EventLog RPC functionality exposed through the EventLog service. The flaw arises from inconsistent handling of a user-supplied event log file between an initial validation step and a later use step. Reported research indicates the vulnerable workflow involves opening a caller-controlled event log file path, validating the EVTX header, and later re-reading the file during a backup operation. By changing the contents of an attacker-controlled SMB-hosted file after the header check but before the subsequent read, an attacker can cause the service to process and write unintended content to a chosen destination on the target system. The issue has been described as enabling remote arbitrary file write and, in practical exploit chains, remote code execution in Active Directory domain networks. Public reporting specifically associates the vulnerable operations with MS-EVEN methods such as ElfrOpenBELW and ElfrBackupELFW.

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.

Successful exploitation can allow an authorized remote attacker to achieve arbitrary code execution on a vulnerable Windows system. The reported exploitation path also provides a remote arbitrary file-write primitive, which can be used to place attacker-controlled content in execution-sensitive locations and then trigger execution through normal system or user activity. In enterprise environments, this can enable compromise of domain-joined hosts, facilitate lateral movement, and provide a foothold for broader post-exploitation activity.

Mitigation

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

Until patches are fully deployed, reduce exposure of the EventLog RPC attack surface by restricting remote access to RPC and SMB from untrusted or unnecessary sources, segmenting administrative and workstation networks, and limiting which principals can authenticate to target hosts. Monitor for anomalous MS-EVEN activity, unusual RPC or SMB requests associated with remote event log operations, suspicious file-write behavior attributable to the EventLog service, and unexpected child-process or persistence artifacts associated with svchost-hosted EventLog activity. Additional hardening of lateral movement paths and minimizing low-privilege network reachability between hosts can reduce exploitability.

Remediation

Patch, then assume compromise.

Apply Microsoft's May 2025 security updates for affected Windows versions. Reported patch references include KB5058392 for Windows 10 and Windows 11 and KB5058411 for Windows Server 2016 through 2025. Organizations should prioritize patching systems where the EventLog RPC surface is reachable across the network, especially domain-connected Windows hosts.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
EventLogin-CVE-2025-29969Repository contains a small Python proof/weaponization set for CVE-2025-29969 (“EventLogin”), described as a TOCTOU issue in the Windows MS-EVEN (Event Log) protocol enabling low-privileged users to write arbitrary files to a remote machine. Structure: - README.md: Explains the vulnerability, prerequisites, and usage examples. Instructs hosting an SMB share via impacket-smbserver with a hardcoded share name 'Share'. - write_file_remotely.py: Weaponized exploit. Connects to the target’s EventLog service over DCERPC named pipe (ncacn_np to \\pipe\\eventlog), authenticates with provided low-privileged credentials, opens an EVTX file via a UNC path on an attacker-controlled SMB share (\\{smb_server_ip}\Share\...), then overwrites a temporary local copy of that EVTX with attacker-chosen file bytes and invokes hElfrBackupELFW to write to an arbitrary remote_file_path. This yields an arbitrary file write primitive on the target (commonly leveraged by writing to Startup folders or other execution points). - check_if_exists.py: Reconnaissance helper (not the full vulnerability). Uses the MS-EVEN hElfrOpenBELW call with a crafted RPC_UNICODE_STRING to probe a remote path and interprets specific NTSTATUS-like error codes to determine whether a file exists, exists as a directory, or does not exist. Useful for enumerating installed software or accessible directories using any domain user credentials. Notable implementation details: - Both scripts craft RPC_UNICODE_STRING with an extra null terminator (MaximumLength += 1), noting an Impacket/EventLog quirk. - Network interaction is entirely over SMB/DCERPC to the EventLog named pipe and (for the write primitive) an SMB file share reachable by the target. Overall purpose: provide an operational exploit to achieve arbitrary remote file write via MS-EVEN, plus a related primitive-based checker to remotely test file existence with low privileges.SafeBreach-Labs · Disclosed Feb 18, 2026 · python · networkOperational
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 CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

Frequently asked questions

Is CVE-2025-29969 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-29969 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-29969?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-29969, the earliest disclosed Feb 18, 2026.
Is there a patch for CVE-2025-29969?
Apply Microsoft's May 2025 security updates for affected Windows versions. Reported patch references include KB5058392 for Windows 10 and Windows 11 and KB5058411 for Windows Server 2016 through 2025.
What products are affected by CVE-2025-29969?
Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, and 14 more.
How severe is CVE-2025-29969?
CVE-2025-29969 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.2% (69th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 activity18Community discussion across Reddit, Mastodon, and other social sources.