CVE-2026-26151
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 ui warning of dangerous operations in Windows Remote Desktop allows an unauthorized attacker to perform spoofing over a network.
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 confidenceWindows Remote Desktop lacks sufficient user interface warnings when users initiate potentially dangerous operations, enabling an unauthenticated remote attacker to perform spoofing attacks over a network by tricking users into connecting to malicious RDP endpoints.
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.9060< 10.0.17763.8644< 10.0.19044.7184< 10.0.19045.7184< 10.0.22631.6936< 10.0.26100.8246< 10.0.26200.8246< 10.0.28000.1836CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
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 against affected rangesOpen Settings > System > About, or run 'winver' command, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command PromptAffected if The installed Windows version is lower than the first version listed in the affected range for your Windows release (e.g., Windows 10 1607 versions below 10.0.14393.9060)
-
Verify RDP is enabledOpen System Properties > Remote tab, or run 'reg query "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections' in Command PromptAffected if The value is 0 (RDP is enabled), indicating the Remote Desktop feature is active and the vulnerable UI warning mechanism applies
-
Confirm NLA status on RDPRun 'reg query "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v UserAuthentication' in Command Prompt, or check via Remote Desktop Connection settingsAffected if The value is 0 (NLA disabled), meaning Network Level Authentication is not required, which increases exposure to unauthenticated remote attacks described in this CVE
Your environment is affected if you are running an unpatched Windows version within the affected ranges AND Remote Desktop is enabled (with or without NLA), as the insufficient UI warning vulnerability exists in the RDP client component regardless of NLA settings.
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.19044.7184
Apply Microsoft security patches for Windows Remote Desktop when available; enable Network Level Authentication (NLA) as an interim control; educate users about verifying RDP connections before accepting certificates.
Install the latest cumulative security update for your specific Windows version from Windows Update or Microsoft Update Catalog - target the minimum fixed build number for your release
- Open Windows Settings and navigate to Windows Update
- Click 'Check for updates' to install the latest cumulative update for your Windows version
- Alternatively, manually install the specific update KB for your Windows version from Microsoft Update Catalog
- For Windows 10 1607 (LTSB): Install update to version 10.0.14393.9060 or later
- For Windows 10 1809: Install update to version 10.0.17763.8644 or later
- For Windows 10 21h2: Install update to version 10.0.19044.7184 or later
- For Windows 10 22h2: Install update to version 10.0.19045.7184 or later
- For Windows 11 23h2: Install update to version 10.0.22631.6936 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26151 — 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-26151 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