dbcve.org
Windows 11 23h2Operating system · Microsoft

CVE-2026-42974

HIGH · 8.1 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.20348.5256 / 10.0.22631.7219 or later.
See remediation →
90/100
Remediation priority · Urgent
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
Integer overflow or wraparound in Windows Performance Monitor allows an unauthorized attacker to execute code 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

An integer overflow vulnerability in Windows Performance Monitor allows an unauthenticated remote attacker to execute arbitrary code by sending specially crafted requests over the network.

MitigationApply Microsoft security updates for Windows Performance Monitor immediately; implement network segmentation and restrict access to affected systems until patches are 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 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269
Windows Server 2022Operating system
Affected:< 10.0.20348.5256
Windows Server 2025Operating system
Affected:< 10.0.26100.32995

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Check Windows build version
    Run 'winver' or 'systeminfo' to obtain the Windows build number, or retrieve it from the registry at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentBuild
    Affected if The build number is below 22631.7219 for Windows 11 23h2, below 26100.8655 for Windows 11 24h2, below 26200.8655 for Windows 11 25h2, below 28000.2269 for Windows 11 26h1, below 20348.5256 for Windows Server 2022, or below 26100.32995 for Windows Server 2025
  2. Verify perfmon.exe exists
    Confirm the presence of perfmon.exe at C:\Windows\System32\perfmon.exe or C:\Windows\SysWOW64\perfmon.exe (on 64-bit systems for 32-bit version)
    Affected if The file exists on the system (the vulnerable component is present)
  3. Check Performance Monitor service
    Run 'Get-Service PerfMon' or check via services.msc to see if the Performance Logs and Alerts service (DiagTrack service dependency) is enabled
    Affected if The service is set to Automatic or is currently running, making the attack surface active

A system is affected if it runs a Windows version with a build number lower than the fixed versions listed and has perfmon.exe present with the Performance Monitor service enabled.

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.5256 / 10.0.22631.7219 / 10.0.26100.8655 or later
Fixed in 10.0.20348.525610.0.22631.721910.0.26100.8655
Interim mitigation

Apply Microsoft security updates for Windows Performance Monitor immediately; implement network segmentation and restrict access to affected systems until patches are deployed.

Recommended fix High confidence

Cumulative security updates for Windows 11 (versions 23h2, 24h2, 25h2, 26h1), Windows Server 2022, and Windows Server 2025 that include the fix for CVE-2026-42974

  1. 1. Identify the current Windows build version by running `winver` or checking Settings > System > About
  2. 2. Determine which Windows version and build you are running (Windows 11 23h2, 24h2, 25h2, 26h1, Server 2022, or Server 2025)
  3. 3. Navigate to Windows Update: Settings > Windows Update > Check for updates
  4. 4. Install all available cumulative updates. The specific security patches for this vulnerability are included in the KB updates for the fixed builds listed
  5. 5. Alternatively, manually download and install the appropriate cumulative update from the Microsoft Update Catalog for your Windows version
  6. 6. After installation, restart the system when prompted
  7. 7. Verify the updated build version meets or exceeds: Windows 11 23h2: 10.0.22631.7219, Windows 11 24h2: 10.0.26100.8655, Windows 11 25h2: 10.0.26200.8655, Windows 11 26h1: 10.0.28000.2269, Windows Server 2022: 10.0.20348.5256, Windows Server 2025: 10.0.26100.32995
Caveat Standard Windows update risks apply - ensure backup of critical data before applying updates

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

Fix this in Windows 11 23h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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