dbcve.org
Windows Server 2012Operating system · Microsoft

CVE-2026-47288

HIGH · 7.1 CVSS v3.1 Developing Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.14393.9234 / 10.0.17763.8880 or later.
See remediation →
73/100
Remediation priority · Elevated
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 Kerberos allows an authorized attacker to execute code over an adjacent 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
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-30.

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 Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.9234
Windows Server 2019Operating system
Affected:< 10.0.17763.8880
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
Adjacent
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

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.20348.5256 or later
Fixed in 10.0.14393.923410.0.17763.888010.0.20348.5256
Recommended fix High confidence

Windows Server 2016: build 10.0.14393.9234+ | Windows Server 2019: build 10.0.17763.8880+ | Windows Server 2022: build 10.0.20348.5256+ | Windows Server 2025: build 10.0.26100.32995+

  1. Identify current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine if the current version falls within the affected version ranges for your Windows Server release
  3. For Windows Server 2016: upgrade to version 10.0.14393.9234 or later
  4. For Windows Server 2019: upgrade to version 10.0.17763.8880 or later
  5. For Windows Server 2022: upgrade to version 10.0.20348.5256 or later
  6. For Windows Server 2025: upgrade to version 10.0.26100.32995 or later
  7. For Windows Server 2012/R2: Microsoft support has ended; migrate to a supported Windows Server version (2016 or later)
  8. Apply the relevant Microsoft Security Update from msrc.microsoft.com for CVE-2026-47288
Caveat Windows Server 2012/R2 is end-of-life with no security updates; requires migration to newer Server version. Test Kerberos-dependent applications after applying updates.

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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