CVE-2026-26183
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 · uneditedImproper access control in Windows RPC API allows an authorized attacker to elevate privileges locally.
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 confidenceImproper access control in the Windows RPC API allows a locally authorized attacker to bypass normal permission checks and elevate their privileges to higher levels on the affected system.
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 dataall versions= r2< 10.0.14393.9060< 10.0.17763.8644< 10.0.20348.5020< 10.0.25398.2274< 10.0.26100.32690CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 Server version and build numberRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows version and build numberAffected if The build number falls within the affected ranges: Server 2016 < 10.0.14393.9060, Server 2019 < 10.0.17763.8644, Server 2022 < 10.0.20348.5020, Server 2022 23h2 < 10.0.25398.2274, Server 2025 < 10.0.26100.32690, or is any version of Server 2012/R2
-
Identify current user privilegesRun 'whoami /groups' or 'whoami /all' to see the current user's group memberships and privilege levelAffected if The current user has local administrative or elevated privileges, as the attacker needs to be a locally authorized user to exploit this vulnerability
-
Check RPC service statusRun 'sc query RPCSS' or check the Remote Procedure Call (RPC) service in services.msc to verify the service is runningAffected if The RPC service is running and exposed, as this is the attack surface for the vulnerability
-
Verify local user account configurationRun 'net user' or check Local Users and Groups (lusrmgr.msc) to enumerate local accountsAffected if Multiple local user accounts exist with varying privilege levels, creating potential attack vectors for privilege escalation
-
Check for existing privilege escalation indicatorsReview security event logs (Event Viewer > Windows Logs > Security) for Event ID 4672 (special privileges assigned) or unusual account modificationsAffected if Unusual privilege assignments or account changes are present that may indicate exploitation attempts
You are affected if your Windows Server version and build number fall within the affected ranges listed above and you have locally authorized users on the system.
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.
dbcve · scoped10.0.14393.906010.0.17763.864410.0.20348.5020
Apply Microsoft security updates for CVE-2026-26183 when released; limit local administrative privileges and follow least-privilege principles to reduce attack surface.
Upgrade to or patch beyond: Windows Server 2016 build 10.0.14393.9060 | Windows Server 2019 build 10.0.17763.8644 | Windows Server 2022 build 10.0.20348.5020 | Windows Server 2022 23h2 build 10.0.25398.2274 | Windows Server 2025 build 10.0.26100.32690. Windows Server 2012/2012 R2: migrate to a suppo
- Identify the current Windows Server version and build number by running 'winver' or 'systeminfo'
- For Windows Server 2016 (build < 10.0.14393.9060): Apply KB5019277 or later security update
- For Windows Server 2019 (build < 10.0.17763.8644): Apply KB5019277 or later security update
- For Windows Server 2022 (build < 10.0.20348.5020): Apply KB5019277 or later security update
- For Windows Server 2022 23h2 (build < 10.0.25398.2274): Apply KB5019277 or later security update
- For Windows Server 2025 (build < 10.0.26100.32690): Apply KB5019277 or later security update
- For Windows Server 2012/2012 R2: Microsoft no longer provides security updates; migrate to a supported Windows Server version
- After patching, verify the build number matches or exceeds the fixed version for your release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26183 — 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-26183 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