dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-27469

HIGH · 7.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.10240.20978 / 10.0.14393.7969 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Uncontrolled resource consumption in Windows LDAP - Lightweight Directory Access Protocol allows an unauthorized attacker to deny service 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 confidence

CVE-2025-27469 is a denial-of-service vulnerability in Windows LDAP (Lightweight Directory Access Protocol) services. The vulnerability stems from uncontrolled resource consumption, allowing an unauthenticated remote attacker to send specially crafted LDAP requests that cause the service to exhaust resources (memory, CPU, or connections) and become unavailable.

MitigationApply the latest Microsoft security updates for Windows Server and Windows Client operating systems that include the LDAP service component. Implement network-level rate limiting or LDAP connection limits at the perimeter as a compensating control until patches can be applied.

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
Windows 10 1507Operating system
Affected:< 10.0.10240.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
Windows 10 1809Operating system
Affected:< 10.0.17763.7136
Windows 10 21h2Operating system
Affected:< 10.0.19044.5737
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Run 'winver' from the command line or check System Properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact build number
    Affected if The build number falls below any of these thresholds: 10.0.10240.20978 (Win10 1507), 10.0.14393.7969 (Win10 1607), 10.0.17763.7136 (Win10 1809), 10.0.19044.5737 (Win10 21h2), 10.0.19045.5737 (Win10 22h2), 10.0.22621.5189 (Win11 22h2), 10.0.22631.5189 (Win11 23h2), 10.0.26100.3775 (Win11 24h2)
  2. Confirm LDAP service is enabled
    Check if the Active Directory Domain Services (AD DS) role, AD LDS role, or Windows LDAP service is installed by running 'Get-WindowsFeature | Where-Object {$_.Name -like "*LDAP*" -or $_.Name -like "*Directory*"}' in PowerShell on servers, or check Services.msc for running directory services on clients
    Affected if LDAP services (AD DS, AD LDS, or Windows LDAP) are installed and running on the system
  3. Check LDAP listener status
    Run 'netstat -an | findstr "389"' or 'netstat -an | findstr "636"' to verify LDAP (389) or LDAPS (636) ports are listening, indicating the LDAP service is exposed
    Affected if The system is listening on LDAP ports 389 or 636, meaning it can receive LDAP requests from the network
  4. Review LDAP service configuration
    Check the LDAP service operational status and event logs for recent resource-related errors by running 'Get-EventLog -LogName System -Source "Microsoft-Windows-LDAP*" -Newest 20' or reviewing the Directory Services event log
    Affected if The LDAP service is running and actively processing requests, with no network-level rate limiting or connection limits configured in front of it

A system is affected if it runs a vulnerable Windows version with LDAP services enabled and exposed to network requests, with the build number falling below the fixed version thresholds for its respective Windows release.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.10240.20978 / 10.0.14393.7969 / 10.0.17763.7136 or later
Fixed in 10.0.10240.2097810.0.14393.796910.0.17763.7136
Interim mitigation

Apply the latest Microsoft security updates for Windows Server and Windows Client operating systems that include the LDAP service component. Implement network-level rate limiting or LDAP connection limits at the perimeter as a compensating control until patches can be applied.

Recommended fix High confidence

Apply Microsoft security update for CVE-2025-27469 to reach the fixed build numbers listed above (e.g., Windows 10 22h2 build 10.0.19045.5737 or later)

  1. Check current Windows build version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Open Windows Settings and navigate to Windows Update (Settings > Update & Security > Windows Update)
  3. Click 'Check for updates' to download and install the latest security updates
  4. Alternatively, manually download the specific security update from the Microsoft Update Catalog (catalog.update.microsoft.com) matching your Windows version
  5. After installation, restart the system to complete the patch process
  6. Verify the update was successful by checking that the build version matches or exceeds: Windows 10 1507: 10.0.10240.20978 | Windows 10 1607: 10.0.14393.7969 | Windows 10 1809: 10.0.17763.7136 | Windows 10 21h2: 10.0.19044.5737 | Windows 10 22h2: 10.0.19045.5737 | Windows 11 22h2: 10.0.22621.5189 | Windows 11 23h2: 10.0.22631.5189 | Windows 11 24h2: 10.0.26100.3775
Caveat Standard risk - patch updates typically have minimal breaking changes; verify compatibility with line-of-business applications before deployment in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27469 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27469 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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