dbcve.org
Windows Server 2022 23h2Operating system · Microsoft

CVE-2025-55697

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.25398.1913 / 10.0.26100.6899 or later.
See remediation →
80/100
Remediation priority · High
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
Heap-based buffer overflow in Azure Local 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 confidence

A heap-based buffer overflow vulnerability exists in Azure Local that allows an authenticated attacker to escalate privileges locally. The vulnerability stems from improper bounds checking when handling certain operations, enabling the attacker to corrupt heap memory and gain higher-level system access.

MitigationApply Microsoft security patches for Azure Local once available; review and restrict local administrative privileges to minimize attack surface until the patch is deployed.

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 Server 2022 23h2Operating system
Affected:< 10.0.25398.1913
Windows Server 2025Operating system
Affected:< 10.0.26100.6899

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
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 checks

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

  1. Identify the Windows Server version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine if the system is Windows Server 2022 23h2 or Windows Server 2025
    Affected if The system is running Windows Server 2022 23h2 or Windows Server 2025
  2. Check the installed build number
    Run 'winver' or 'systeminfo | findstr /C:"Build Number"' to obtain the full build version (for example, 10.0.25398.xxxx)
    Affected if The build number is less than 10.0.25398.1913 for Server 2022 23h2, or less than 10.0.26100.6899 for Server 2025
  3. Confirm Azure Local is installed
    Check for Azure Local components by reviewing installed programs via 'Get-WmiObject -Class Win32_Product' or checking for Azure Local-specific services in 'services.msc'
    Affected if Azure Local or related Azure Stack HCI management components are present on the system
  4. Verify local authentication context
    Run 'whoami /groups' to list current user group memberships and determine if the account has local administrative privileges
    Affected if The user has local administrator rights on the affected system, which is required for the authenticated attacker to exploit this vulnerability

The environment is affected if the system runs Windows Server 2022 23h2 with build < 10.0.25398.1913 or Windows Server 2025 with build < 10.0.26100.6899, has Azure Local components installed, and supports authenticated local users with administrative access.

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.25398.1913 / 10.0.26100.6899 or later
Fixed in 10.0.25398.191310.0.26100.6899
Interim mitigation

Apply Microsoft security patches for Azure Local once available; review and restrict local administrative privileges to minimize attack surface until the patch is deployed.

Recommended fix High confidence

Windows Server 2022 23h2: upgrade to 10.0.25398.1913 or later; Windows Server 2025: upgrade to 10.0.26100.6899 or later

  1. Open Windows Update on the affected Windows Server (2022 23h2 or 2025)
  2. Check for and install all available updates, specifically looking for the security update containing version 10.0.25398.1913 (Server 2022 23h2) or 10.0.26100.6899 (Server 2025)
  3. Alternatively, download the specific KB update from the Microsoft Update Catalog matching your server version
  4. Restart the server after applying the update
  5. Verify the installed version matches or exceeds the fixed release by running 'winver' or checking System Information
Caveat Standard Windows Server update considerations apply; ensure backups and cluster validations are performed for Azure Local deployments

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

Fix this in Windows Server 2022 23h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55697 — 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-55697 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