dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-42914

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.14393.9234 / 10.0.17763.8880 or later.
See remediation →
59/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
Out-of-bounds read in Windows Kerberos 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

This is an out-of-bounds read vulnerability in Windows Kerberos authentication service. An attacker with valid credentials can trigger the vulnerability by sending specially crafted network requests to a Windows system running Kerberos, causing the service to read beyond allocated memory bounds and potentially crash, resulting in denial of service.

MitigationApply Microsoft security updates for CVE-2026-42914 to all affected Windows systems, prioritizing domain controllers and servers running Kerberos authentication services; verify Kerberos authentication functionality after patching.

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 1607Operating system
Affected:< 10.0.14393.9234
Windows 10 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
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

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

CVSS:3.1/AV:N/AC:H/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 installed Windows version and build number
    Open Command Prompt or PowerShell and run: winver or systeminfo | findstr /B /C:"OS Version" or [System.Environment]::OSVersion.Version.ToString()
    Affected if The displayed build number is lower than any of these thresholds: 14393.9234 (Win10 1607), 17763.8880 (Win10 1809), 19044.7417 (Win10 21h2), 19045.7417 (Win10 22h2), 22631.7219 (Win11 23h2), 26100.8655 (Win11 24h2), 26200.8655 (Win11 25h2), or 28000.2269 (Win11 26h1)
  2. Confirm Kerberos is in use
    Check if the system is domain-joined: run dsregcmd /status in Command Prompt; look for AzureAdJoined or DomainJoined status, or check registry key HKLM\SYSTEM\CurrentControlSet\Services\Kerberos\Parameters for a valid DefaultDomain value
    Affected if The system is domain-joined or has Kerberos authentication configured (Kerberos is enabled by default on all domain-joined Windows systems)
  3. Assess network exposure of Kerberos services
    Run netstat -an | findstr ":88" to check if Kerberos ports (88/TCP and 88/UDP) are listening, indicating the system is acting as a Kerberos server or is reachable on these ports
    Affected if Port 88 is listening and accessible from network locations outside the trusted authentication server pool

The system is affected if its Windows build number falls below the fixed version thresholds AND Kerberos is enabled AND the system has network accessibility on Kerberos ports.

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.14393.9234 / 10.0.17763.8880 / 10.0.19044.7417 or later
Fixed in 10.0.14393.923410.0.17763.888010.0.19044.7417
Interim mitigation

Apply Microsoft security updates for CVE-2026-42914 to all affected Windows systems, prioritizing domain controllers and servers running Kerberos authentication services; verify Kerberos authentication functionality after patching.

Recommended fix Moderate confidence

For Windows 10 1607: upgrade to 10.0.14393.9234 or later | Windows 10 1809: upgrade to 10.0.17763.8880 or later | Windows 10 21h2: upgrade to 10.0.19044.7417 or later | Windows 10 22h2: upgrade to 10.0.19045.7417 or later | Windows 11 23h2: upgrade to 10.0.22631.7219 or later | Windows 11 24h2: upgr

  1. Open Windows Settings on the affected system
  2. Navigate to Windows Update or use WSUS/Intune to check for available updates
  3. Install the cumulative update that includes the fix for CVE-2026-42914
  4. Restart the system as required to complete the installation
  5. Verify the installed version matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks: ensure backups exist and test compatibility with critical applications before deploying broadly

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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