CVE-2025-48814
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 · uneditedMissing authentication for critical function in Windows Remote Desktop Licensing Service allows an unauthorized attacker to bypass a security feature 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 confidenceThis vulnerability in Windows Remote Desktop Licensing Service lacks authentication for a critical function, enabling an unauthenticated remote attacker to bypass a security mechanism over the network. The issue allows unauthorized access to licensing operations that should require authentication. Successful exploitation could allow attackers to manipulate or bypass Remote Desktop licensing controls.
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.8246< 10.0.17763.7558< 10.0.19044.6093< 10.0.19045.6093< 10.0.22621.5624< 10.0.22631.5624< 10.0.26100.4652= 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 if Remote Desktop Licensing Service is installedOpen Services console (services.msc) and look for 'Remote Desktop Licensing' service, or run: Get-Service -Name 'TermServLicensing' in PowerShellAffected if The service exists and is installed on the system
-
Verify Windows version against affected rangesRun 'winver' or execute 'Get-ComputerInfo | Select-Object OsName,OsVersion,OsBuildNumber' in PowerShellAffected if The installed Windows version and build number fall below the patched versions listed for your Windows release
-
Confirm the licensing service is runningRun 'Get-Service -Name TermServLicensing' or check in Services console - look for Status of 'Running'Affected if The Remote Desktop Licensing service is currently running
-
Check for exposed RDP licensing portsRun 'netstat -an | findstr /i "3389"' or use PowerShell 'Get-NetTCPConnection -LocalPort 3389,3390 -State Listen' to see if licensing ports are listeningAffected if The system is listening on RDP licensing ports (3389, 3390) and is network-accessible
-
Review Remote Desktop Services configurationOpen Group Policy Editor (gpedit.msc) and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing, or check registry key HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal ServicesAffected if Remote Desktop Licensing is configured and the service is enabled as the licensing mode
A system is affected if it runs a vulnerable Windows version below the patched builds AND has the Remote Desktop Licensing service installed and running with network-accessible licensing ports.
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.824610.0.17763.755810.0.19044.6093
Apply the appropriate Microsoft security update for Windows Remote Desktop Licensing Service. Until patched, restrict network access to RDP licensing ports via firewall rules and disable the service if not required.
Windows 10 1607: 10.0.14393.8246+ | Windows 10 1809: 10.0.17763.7558+ | Windows 10 21h2: 10.0.19044.6093+ | Windows 10 22h2: 10.0.19045.6093+ | Windows 11 22h2: 10.0.22621.5624+ | Windows 11 23h2: 10.0.22631.5624+ | Windows 11 24h2: 10.0.26100.4652+ | Windows Server 2008 R2: Migrate to supported ver
- Identify the exact Windows version and build number by running 'winver' or 'systeminfo' in command prompt
- Determine which affected product category applies (Windows 10 version, Windows 11 version, or Windows Server 2008 R2)
- Open Windows Update by pressing Win+R, typing 'ms-settings:windowsupdate', and pressing Enter
- Check for updates and install all available security updates, or manually download the specific KB update for your Windows version from Microsoft Update Catalog
- Restart the system after installing the update
- Verify the installation was successful by checking the build number matches or exceeds: 10.0.14393.8246 (Win10 1607), 10.0.17763.7558 (Win10 1809), 10.0.19044.6093 (Win10 21h2), 10.0.19045.6093 (Win10 22h2), 10.0.22621.5624 (Win11 22h2), 10.0.22631.5624 (Win11 23h2), or 10.0.26100.4652 (Win11 24h2)
- For Windows Server 2008 R2, note that extended support ended; consider migrating to a supported Windows Server version if still on this platform
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48814 — 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-2025-48814 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