dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-48802

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.20348.3932 / 10.0.22621.5624 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Improper certificate validation in Windows SMB allows an authorized 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 · low confidence

This is a certificate validation vulnerability in Windows SMB (Server Message Block) protocol. An authorized attacker can exploit improper certificate validation to perform spoofing attacks over the network, potentially allowing man-in-the-middle attacks or impersonation of legitimate SMB servers.

MitigationApply Microsoft security updates for Windows when available. Ensure SMB connections use properly validated certificates and consider network segmentation to limit exposure to authorized attackers.

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 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows Server 2022Operating system
Affected:< 10.0.20348.3932
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1732

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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

  1. Verify Windows build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /C:"Build"' to obtain the OS build number
    Affected if The build number is below 10.0.22621.5624 for Windows 11 22h2, below 10.0.22631.5624 for Windows 11 23h2, below 10.0.20348.3932 for Windows Server 2022, or below 10.0.25398.1732 for Windows Server 2022 23h2
  2. Confirm SMB is enabled
    Run 'Get-SmbServerConfiguration' in PowerShell and check the 'EnableSMB1Protocol' or 'EnableSMB2Protocol' status, or run 'sc query mrxsmb10' to check if the SMB service is running
    Affected if SMB protocol is enabled and the Windows build version is in the affected range
  3. Check SMB signing configuration
    Run 'Get-SmbServerConfiguration | Select-Object RequireSecuritySignature' in PowerShell to check if SMB signing is required on the server, or run 'Get-SmbConnection' to see active SMB connections
    Affected if SMB is configured without requiring signed connections and the Windows build version is in the affected range
  4. Inspect SMB certificate authentication settings
    Check if SMB over TLS or SMB signing with certificates is configured by examining 'Get-SmbServerConfiguration' output for 'EncryptData' or by reviewing SMB share certificates via 'Get-SmbShare' with 'EncryptData' property
    Affected if SMB uses certificate-based authentication or encryption and the Windows build version is in the affected range

A system is affected if it runs any of the specified Windows versions below the fixed build numbers AND has SMB protocol enabled, particularly when SMB signing or certificate authentication is in use.

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.20348.3932 / 10.0.22621.5624 / 10.0.22631.5624 or later
Fixed in 10.0.20348.393210.0.22621.562410.0.22631.5624
Interim mitigation

Apply Microsoft security updates for Windows when available. Ensure SMB connections use properly validated certificates and consider network segmentation to limit exposure to authorized attackers.

Recommended fix High confidence

Windows 11 22h2 to build 10.0.22621.5624 or later | Windows 11 23h2 to build 10.0.22631.5624 or later | Windows Server 2022 to build 10.0.20348.3932 or later | Windows Server 2022 23h2 to build 10.0.25398.1732 or later

  1. Open Windows Settings on the affected system
  2. Navigate to Windows Update (Settings > Windows Update)
  3. Click 'Check for updates' to retrieve available updates
  4. Install all recommended updates, specifically looking for the security update containing build 10.0.22621.5624 (Windows 11 22h2), 10.0.22631.5624 (Windows 11 23h2), 10.0.20348.3932 (Windows Server 2022), or 10.0.25398.1732 (Windows Server 2022 23h2)
  5. Restart the system when prompted to complete the update installation
  6. Verify the installed version by running 'winver' or checking System Properties to confirm the build number matches or exceeds the fixed version
Caveat Standard Windows update; may require restart and should be tested in non-production environment first

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

Fix this in Windows 11 22h2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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