CVE-2026-102634
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-102634 is a high-severity Use of Multiple Resources with Duplicate Identifier (CWE-694) vulnerability. Its CVSS base score is 8.7 (High).
Operationally, ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to IA-4 (Identifier Management) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-89029
Vulnerability Data
SGLang through 0.5.20 in prefill/decode disaggregation mode fails to validate duplicate bootstrap_room fields in /generate requests with Mooncake KV transfer backend. Unauthenticated attackers can send concurrent requests with identical bootstrap_room values to crash scheduler processes or hang other users' requests…
more
until transfer timeout.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V8.4.1V3.5.4V6.8.1V9.2.4
Mitigating Controls (NIST 800-53 r5) AI
Identifier management directly requires authorization and uniqueness controls that stop duplicate resource identifiers from being assigned or used.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Maintaining software/service inventories requires and enforces unique identifiers to avoid collisions.
Lifecycle management of assets includes identifier uniqueness as a supporting practice.
Managing identities and credentials for users/services/hardware directly requires unique identifiers.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.16(e) directly requires avoiding duplicate identities in one domain (the exact condition CWE-694 names), and (a)-(c) further constrain identity issuance to prevent the duplicate-identifier situation from arising; this stops exploitation in the identity-management slice of the weakness but leaves other resource types (non-identity) and cross-domain cases untouched.
Secure development lifecycle practices can catch duplicate-ID issues during design and code review.