Critical CVSS 8.1 EPSS 0.17324 🔬 Patch diffed 2025-06 archive

Executive Summary

Use after free in Windows KDC Proxy Service (KPSSVC) allows an unauthorized attacker to execute code over a network.

Overview

8.1
CVSS HIGH
Critical
MS Severity
Not Exploited
MS Exploit Status
More Likely
MS Exploit Likelihood
Category Remote Code Execution
Released Jun 10 2025
Last Updated Jun 10 2025
Publicly Disclosed No
CISA KEV Not Listed
Known Exploits None Known
EPSS Score 0.17324 — 0.96834 percentile
NVD CVSS 8.1 HIGH — matches MSRC

CVSS Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
ATTACK VECTOR
Network
ATTACK COMPLEXITY
High
PRIVILEGES REQUIRED
None
USER INTERACTION
None
SCOPE
Unchanged
CONFIDENTIALITY
High
INTEGRITY
High
AVAILABILITY
High
EXPLOIT CODE MATURITY
Unproven
REMEDIATION LEVEL
Official Fix
REPORT CONFIDENCE
Confirmed
Temporal Score: 7.1

EPSS Score

0.17324
probability of exploitation in the next 30 days
0.96834 percentile - updated 2026-08-14
View on FIRST.org

Affected Products

9 affected products
Product KB Article Severity Impact Restart Required
Windows Server 2012 5061059 (Monthly Rollup) Critical Remote Code Execution Yes
Windows Server 2012 (Server Core installation) 5061059 (Monthly Rollup) Critical Remote Code Execution Yes
Windows Server 2012 R2 5061018 (Monthly Rollup) Critical Remote Code Execution Yes
Windows Server 2012 R2 (Server Core installation) 5061018 (Monthly Rollup) Critical Remote Code Execution Yes
Windows Server 2016 5061010 (Security Update) Critical Remote Code Execution Yes
Windows Server 2016 (Server Core installation) 5061010 (Security Update) Critical Remote Code Execution Yes
Windows Server 2019 5060531 (Security Update) Critical Remote Code Execution Yes
Windows Server 2019 (Server Core installation) 5060531 (Security Update) Critical Remote Code Execution Yes
Windows Server 2022 5060526 (Security Update) 5060525 (SecurityHotpatchUpdate) Critical Remote Code Execution 5058385 5058500 Base: 8.1 Temporal: 7.1 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.20348.3807 10.0.20348.3745 Yes None Windows Server 2022 (Server Core installation) 5060526 (Security Update) 5060525 (SecurityHotpatchUpdate) Critical Remote Code Execution 5058385 5058500 Base: 8.1 Temporal: 7.1 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.20348.3807 10.0.20348.3745 Yes None Windows Server 2022, 23H2 Edition (Server Core installation) 5060118 (Security Update) Critical Remote Code Execution Yes

Patches

5 patches
Article Type Restart
5061059 Monthly Rollup Yes
5061018 Monthly Rollup Yes
5061010 Security Update Yes
5060531 Security Update Yes
5060118 Security Update Yes

Patch Diff

ghidriff · kpssvc.dll (KB5060842)

Use-after-free (CWE-416, race-triggered) in the Windows KDC Proxy Service kpssvc.dll (KPSSVC, MS-KKDCP), unauthenticated remote code execution against servers configured as a KDC Proxy (Critical, AV:N, AC:H race, CVSS 8.1). Each proxied Kerberos request is tracked by a _KPS_IO context created by KpsCreateKpsIo and released by KpsFreeKpsIo, driven asynchronously through HTTP receive/send and backend-socket stages each with its own I/O completion routine (KpsHttp*IoCompletion, KpsSocket*IoCompletion) operating on the same _KPS_IO. PRE: the _KPS_IO could be freed by one path (cancel/timeout/completion) while another in-flight completion still referenced it - a race UAF. Because KPSSVC accepts KKDCP requests over the network without authentication, the freed-object reuse is an RCE primitive (Microsoft rates it Critical; domain controllers are not affected - only servers configured as KDC Proxy). Diff of kpssvc.dll 10.0.26100.3912 -> .4343 (Jun 10 2025, KB5060842, Windows Server 2025; OS fixed build .4349; vsize 274432 -> 286720) confirms the fix: a KpsIoLockedRef locked-reference wrapper is introduced (gated behind CFR flag Feature_4205429049) and threaded through the request paths - KpsProcessProxyRequest's signature changes from _KPS_IO* to KpsIoLockedRef&, so the context is held alive/serialized while in use and KpsFreeKpsIo (now paired with KpsCancelTimeoutTimer) releases it only once no locked reference remains. Stated at confirmed-changed level (broad async-lifecycle rework; the isolable mechanism is the KpsIoLockedRef reference lifetime management).

Pre-patch version 10.0.26100.3912 Download
Post-patch version 10.0.26100.4343 Download
Function Address Change Note
KpsProcessProxyRequest code change code (now takes a KpsIoLockedRef locked reference instead of a raw _KPS_IO*) Signature changed from KpsProcessProxyRequest(_KPS_IO*) to KpsProcessProxyRequest(KpsIoLockedRef&) - the request context is now held via a locked reference across processing so it cannot be freed while in use.
KpsFreeKpsIo / KpsCreateKpsIo code change code (request-context lifecycle reworked, CFR-gated) KpsFreeKpsIo now pairs with KpsCancelTimeoutTimer and releases the _KPS_IO only once no locked reference remains (Feature_4205429049); the async completion routines (Kps*IoCompletion) acquire/hold the locked reference.
Feature_4205429049 gate added (CFR gate) Dominant CFR flag gating the KpsIoLockedRef locked-reference lifecycle; the original raw-pointer _KPS_IO handling remains when the flag is disabled.
View full diff report View RCA report

Root Cause Analysis

CVE-2025-33071 — Windows KDC Proxy Service kpssvc.dll Request-Context Race → Use-After-Free (Unauthenticated RCE)


Summary

Product Windows — kpssvc.dll (KDC Proxy Service / KPSSVC, [MS-KKDCP])
CVE ID CVE-2025-33071
Impact Remote Code Execution (unauthenticated, network)
MSRC severity Critical
CVSS 8.1 / 7.1 — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CWE CWE-416: Use After Free (race-triggered)
Affected role Windows Servers configured as a KDC Proxy (KKDCP) server (domain controllers are not affected, per MSRC)
Delivery Network — crafted KKDCP requests to the proxy; win a race (AC:H)
KB / Fixed build KB5060842 — kpssvc.dll 10.0.26100.4343 (Windows Server 2025, build 26100; OS fixed build 10.0.26100.4349)
Patch Date June 10, 2025 (2025-Jun)
Pre-patch binary kpssvc.dll 10.0.26100.3912 — SHA256 de28e58abf562d7e1f5946233a6bd20d30fcee22185d791840707a917c341c2b
Post-patch binary kpssvc.dll 10.0.26100.4343 — SHA256 3471e19223648c485e1f95f148880bec59b8f4e162f6cd0f2b955b471875308c
Feature flag Feature_4205429049 — the fix is CFR-gated
Exploitability Exploitation More Likely; not publicly disclosed; not exploited (per MSRC)

Product note: KDC Proxy (KPSSVC) is a Server role; MSRC lists this CVE for Windows Server (2012–2025), not the 24H2 client. The kpssvc.dll binary is the same 26100-based code; this diff is the Server-2025 May→June pair.


Product Description

kpssvc.dll implements the KDC Proxy Service (KPSSVC) — the [MS-KKDCP] server that proxies Kerberos AS/TGS exchanges over HTTPS. Each proxied request is tracked by a _KPS_IO context object created by KpsCreateKpsIo and released by KpsFreeKpsIo. The request is driven asynchronously through HTTP receive/send and backend-socket connect/receive stages, each with an I/O completion routine (KpsHttp*IoCompletion, KpsSocket*IoCompletion) that operates on the same _KPS_IO.


Vulnerability Summary

The _KPS_IO request context is shared across concurrent asynchronous stages (HTTP receive, backend socket I/O, cancellation, timeout). Pre-patch, one path could free the _KPS_IO while another in-flight completion / cancellation still referenced it — a race (AC:H — “requires an attacker to win a race condition”) that yields a use-after-free of the request context (CWE-416). Because KPSSVC accepts KKDCP requests over the network without authentication (AV:N, PR:N), the freed-object reuse is a remote code-execution primitive against a server configured as a KDC Proxy (Microsoft rates it Critical).

Confirmation level: this June update is a broad KPSSVC async-lifecycle rework (15 code-changed + 21 added + 67 modified functions) under the dominant flag Feature_4205429049. The isolable mechanism is the introduction of a KpsIoLockedRef locked-reference wrapper that holds the _KPS_IO alive across its use; stated here at confirmed-changed level.


Prerequisites and Constraints

  • Network, unauthenticated (AV:N, PR:N, UI:N) against a KDC Proxy server.
  • AC:H: win the race between a request-context teardown (cancel/timeout/completion) and an in-flight completion that still uses the _KPS_IO.
  • Result: the _KPS_IO is freed while still referenced → use-after-free.

Vulnerability Details

Root Cause

The _KPS_IO request context’s lifetime was not safely synchronized across the concurrent async stages, so a teardown could free it while another completion routine was still operating on it.

The patch (confirmed — diff, .3912 → .4343)

The diff introduces a KpsIoLockedRef reference/lock wrapper around the _KPS_IO and threads it through the request-processing paths (gated behind Feature_4205429049). The clearest signal is the signature change of KpsProcessProxyRequest, which now takes a locked reference instead of a raw pointer, so the context is held alive (and serialized) while in use:

// PRE (10.0.26100.3912):
void KpsProcessProxyRequest(_KPS_IO *ctx);                 // raw pointer to the request context

// POST (10.0.26100.4343) — PATCHED (from the diff):
void KpsProcessProxyRequest(KpsIoLockedRef &ref);          // *** locked reference holds _KPS_IO alive ***
// ... under Feature_4205429049, the async stages acquire/hold a KpsIoLockedRef on the
//     _KPS_IO; KpsFreeKpsIo (now paired with KpsCancelTimeoutTimer) releases the
//     context only once no locked reference remains, so a teardown can no longer free
//     it while an in-flight completion still references it.

By taking and holding a KpsIoLockedRef on the _KPS_IO across the receive / socket / cancel / completion stages, the context can no longer be freed while another stage is using it, closing the race use-after-free.

Patch Completeness Assessment

CFR-gated behind Feature_4205429049. The locked-reference lifecycle runs only when the flag is enabled; the original raw-pointer handling remains when disabled. Verify Feature_4205429049 is enabled to confirm the fix is live. Given unauthenticated network RCE against KDC Proxy servers, apply KB5060842 (Server 2025) / the appropriate June 2025 update regardless.


Detection Guidance

Behavioural. Use-after-free / heap-corruption crashes in the KPSSVC service — kpssvc!KpsProcessProxyRequest, KpsFreeKpsIo, and the Kps*IoCompletion routines — on unpatched/flag-disabled KDC Proxy servers, correlated with bursts of KKDCP (HTTPS) requests and cancellations/timeouts. Restrict KDC Proxy (KKDCP, TCP/443) exposure and apply the June 2025 update on KDC-Proxy-configured servers.

Config. The fix is CFR-gated — confirm Feature_4205429049 is enabled.


References

  • MSRC advisory — CVE-2025-33071 (Windows KDC Proxy Service (KPSSVC) Remote Code Execution), released 2025-06-10, KB5060842 (Server 2025).
  • [MS-KKDCP]: Kerberos Key Distribution Center (KDC) Proxy Protocol.
  • Full binary diff: /data/patch_diffs/kpssvc_dll-cve-2025-33071-ghidriff.md

Attack Path

A race between request-context teardown and an in-flight KKDCP completion frees the _KPS_IO while still in use

Attack path for CVE-2025-33071 A race between request-context teardown and an in-flight KKDCP completion frees the _KPS_IO while still in use 01 — ENTRY Unauthenticated attacker sends crafted KKDCP requests to a KDC Proxy server kpssvc processes each proxied Kerberos request via a _KPS_IO context driven through async HTTP/socket stages. AV:N / PR:N / UI:N (network, no auth). 02 — CONTROLLED INPUT Drives concurrent completion / cancellation on the same request AC:H - the attacker must win the race between a teardown (cancel/timeout/completion) and an in-flight completion that still references the _KPS_IO. 03 — MISSING CHECK _KPS_IO freed while still referenced (CWE-416) Pre-patch one path frees the request context while another in-flight completion is still using it - a use-after-free of the _KPS_IO. 04 — IMPACT Freed request context reused -> remote code execution The freed _KPS_IO is reclaimed/reused, giving an unauthenticated network attacker code execution in the KDC Proxy service (Critical).

Derived from the patch delta: the checks added by the vendor identify which fields crossed a trust boundary unvalidated. Reachability and privilege are taken from the call chain in the RCA report.

Exploits & PoC

Detection Rules

Acknowledgments

k0shl
ʌ!ɔ⊥ojv with Kunlun Lab