dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-33057

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.10240.21034 / 10.0.14393.8148 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
Null pointer dereference in Windows Local Security Authority (LSA) allows an authorized 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

A null pointer dereference vulnerability exists in Windows Local Security Authority (LSA) that can be exploited by an authenticated attacker to cause a denial of service condition. The vulnerability can be triggered remotely over a network, causing the LSA to fail.

MitigationApply Microsoft security updates for CVE-2025-33057 when available. Prioritize patching domain controllers and systems handling authentication as LSA is critical to Windows authentication. Test patches in a non-production environment before deployment.

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.21034
Windows 10 1607Operating system
Affected:< 10.0.14393.8148
Windows 10 1809Operating system
Affected:< 10.0.17763.7434
Windows 10 21h2Operating system
Affected:< 10.0.19044.5965
Windows 10 22h2Operating system
Affected:< 10.0.19045.5965
Windows 11 22h2Operating system
Affected:< 10.0.22621.5472
Windows 11 23h2Operating system
Affected:< 10.0.22631.5472
Windows 11 24h2Operating system
Affected:< 10.0.26100.4270

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Check Windows version and build number
    Run 'winver' to see the version and build, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt
    Affected if The displayed build number falls below the minimum fixed version for your Windows release (e.g., < 10.0.10240.21034 for Windows 10 1507, < 10.0.14393.8148 for Windows 10 1607, etc.)
  2. Confirm exact build number via registry
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' in Command Prompt
    Affected if The CurrentBuild value is lower than the threshold for your specific Windows version and build (e.g., for Windows 10 22h2 the threshold is 19045.5965)
  3. Verify LSA service is running
    Run 'sc query lsass' in Command Prompt or open Services and locate "Local Security Authority Process"
    Affected if The service state shows as RUNNING (LSA is a core Windows component and should always be running; its presence confirms the vulnerable component exists)
  4. Check Windows Update for installed security patches
    Run 'wmic qfe list' or open Settings > Windows Update > Update history to see installedKB updates
    Affected if No security update corresponding to CVE-2025-33057 appears in the installed updates list

You are affected if your Windows version build number is lower than the fixed version for your specific Windows release and the CVE-2025-33057 security update is not installed.

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.21034 / 10.0.14393.8148 / 10.0.17763.7434 or later
Fixed in 10.0.10240.2103410.0.14393.814810.0.17763.7434
Interim mitigation

Apply Microsoft security updates for CVE-2025-33057 when available. Prioritize patching domain controllers and systems handling authentication as LSA is critical to Windows authentication. Test patches in a non-production environment before deployment.

Recommended fix High confidence

Apply the May 2025 (or subsequent) Windows Security Update containing the CVE-2025-33057 fix for your specific Windows version (e.g., Windows 10 22h2 build >=10.0.19045.5965)

  1. Identify the exact Windows version installed by running 'winver' or 'systeminfo' in Command Prompt
  2. Navigate to https://msrc.microsoft.com/update-guide to find the security update for CVE-2025-33057
  3. Download and install the appropriate monthly security update for your Windows version from Microsoft Update Catalog
  4. Restart the system after applying the update to ensure the LSA security fix takes effect
  5. Verify the update was installed successfully by checking Windows Update history or running 'systeminfo' again
Caveat Standard Windows security update; may require system restart; no expected breaking changes for typical configurations

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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