CVE-2026-50502
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient granularity of access control in Windows Event Logging Service allows an authorized attacker to execute code over a network.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInsufficient granularity of access control in Windows Event Logging Service allows an authorized attacker to execute code over a network. The vulnerability stems from inadequate permission boundaries within the event logging subsystem, potentially permitting a user with limited privileges to escalate or inject code through manipulated event log requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.14393.9339< 10.0.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2525all versions= r2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Windows version and build numberRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' or use PowerShell: [System.Environment]::OSVersion.VersionAffected if The displayed build number is lower than the threshold for your Windows version (10.0.14393.9339 for 1607, 10.0.17763.9020 for 1809, 10.0.19044.7548 for 21h2, 10.0.19045.7548 for 22h2, 10.0.26100.8875 for 11 24h2, 10.0.26200.8875 for 11 25h2, 10.0.28000.2525 for 11 26h1). For Windows Server 2012 or
-
Confirm Windows edition and releaseRun 'winver' to see if the system is Windows 10 1607, 1809, 21h2, 22h2, Windows 11 24h2/25h2/26h1, or Windows Server 2012/2012 R2Affected if The system matches any of the affected product versions listed in the CVE.
-
Verify Event Logging Service is presentRun 'sc query wevtsvc' or check service status via PowerShell: Get-Service -Name 'EventLog'Affected if The Event Log service exists and is installed on the system, which is default for all affected Windows versions.
-
Check if running an unpatched Event Logging subsystemReview installed Windows updates: run 'Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10' or check Windows Update history for recent security patches related to Event LoggingAffected if No recent security updates addressing Event Logging access control are installed, or the build number remains below the patched threshold.
You are affected if your Windows version and build number fall below the specified thresholds for your product, or if you run Windows Server 2012/2012 R2 and have not applied the relevant security patch.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data10.0.14393.933910.0.17763.902010.0.19044.7548
Apply Microsoft security patches for Windows Event Logging Service as they become available through standard Windows Update channels. Verify that event logging functionality continues to operate correctly after patching.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50502 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data