CVE-2025-62468
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 · uneditedOut-of-bounds read in Windows Defender Firewall Service allows an authorized attacker to disclose information 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 confidenceThis is an out-of-bounds read vulnerability in Windows Defender Firewall Service that allows a locally authorized attacker to read sensitive information from memory beyond intended boundaries. The flaw stems from improper bounds checking in the firewall service component, enabling disclosure of potentially sensitive data to an authenticated local user.
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.22631.6345< 10.0.26100.7392< 10.0.26200.7392< 10.0.25398.2025< 10.0.26100.7392CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 Windows build versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the full build number, or run 'ver' at command promptAffected if Build number is below 10.0.22631.6345 (Win11 23h2), 10.0.26100.7392 (Win11 24h2/Server 2025), 10.0.26200.7392 (Win11 25h2), or 10.0.25398.2025 (Server 2022 23h2)
-
Verify Windows Defender Firewall service is runningOpen Services (services.msc) and locate 'Windows Defender Firewall', or run 'sc query MpsSvc' at command promptAffected if The Windows Defender Firewall service (MpsSvc) is in a running state - the flaw exists in this service component
-
Confirm firewall is enabledRun 'netsh advfirewall show allprofiles' or check via Windows Security app under Firewall & network protectionAffected if Firewall is enabled for any profile (Domain, Private, or Public) - the vulnerable code path is active when firewall is running
-
Check current user privilegesRun 'whoami /groups' or 'whoami /all' to see if you have administrative privilegesAffected if User has local administrative rights - the CVSS indicates this is a locally authorized attacker scenario
Your environment is affected if you are running an unpatched Windows 11 (23h2/24h2/25h2) or Windows Server 2022/2025 build below the thresholds listed AND the Windows Defender Firewall service is running.
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.22631.634510.0.25398.202510.0.26100.7392
Apply Microsoft security updates for Windows Defender Firewall when released. Until a patch is available, restrict local administrative access and monitor system logs for anomalous firewall service behavior.
Windows 11 23h2: build 10.0.22631.6345 or later | Windows 11 24h2: build 10.0.26100.7392 or later | Windows 11 25h2: build 10.0.26200.7392 or later | Windows Server 2022 23h2: build 10.0.25398.2025 or later | Windows Server 2025: build 10.0.26100.7392 or later
- Open Settings > Windows Update and check for updates
- Install all available cumulative updates for your Windows version
- After installation, verify the build number matches or exceeds the fixed version (KB reference: MSRC-CVE-2025-62468)
- Restart the system if prompted to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62468 — 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-62468 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