Security Resilience

CVE-2026-96599

Crypto Weakness

Public PoCCrypto Weakness
Published
23 September 2026
Modified
24 September 2026
CVSS Score v4 8.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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:X
EPSS Score 0.0046 40th percentile
Risk Priority 35 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-96599 is a high-severity Use of Insufficiently Random Values (CWE-330) vulnerability. Its CVSS base score is 8.2 (High).

Operationally, ranked at the 40th 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 SC-12 (Cryptographic Key Establishment and Management) and SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Isotope eCommerce through 2.9.10 derives order identifiers from uniqid() instead of a cryptographically secure source, allowing unauthenticated attackers to guess identifiers. Guest orders lack ownership verification, enabling attackers to access order details including billing address, customer information, and purchased files…

more

by supplying a guessed uid parameter.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-34353Shared CWE-330
CVE-2024-28013Shared CWE-330
CVE-2024-48928Shared CWE-330
CVE-2024-10604Shared CWE-330
CVE-2025-49198Shared CWE-330
CVE-2026-20101Shared CWE-330
CVE-2024-0761Shared CWE-330
CVE-2025-10745Shared CWE-330
CVE-2023-22912Shared CWE-330
CVE-2025-4607Shared CWE-330

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

SC-12 requires proper cryptographic key establishment and management, which structurally mandates use of sufficient randomness for key generation.

SC-13 requires selection and implementation of approved cryptographic algorithms and methods, which inherently depend on and enforce sufficiently random values.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

blocks

Cryptographic controls require use of approved, sufficiently random values for keys and nonces.

finds

Security testing can detect weak randomness but does not prescribe the control itself.

prevents

Secure coding standards explicitly prohibit use of weak or predictable random number generators.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References