Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NSummary
CVE-2026-23684 is a medium-severity Race Condition within a Thread (CWE-366) vulnerability in Sap Commerce Cloud. Its CVSS base score is 5.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-6459
Vulnerability Data
A race condition vulnerability exists in the SAP Commerce cloud. Because of this when an attacker adds products to a cart, it may result in a cart entry being created with erroneous product value which could be checked out. This…
more
leads to high impact on data integrity, with no impact on data confidentiality or availability of the application.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V10.4.2V10.4.5V15.1.3V15.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can include concurrency and stress testing that finds race conditions after they have been coded.
Requiring documented development standards and tools can mandate use of safe concurrency patterns that avoid introducing races.
Security engineering principles include requirements for synchronization primitives and thread-safe design that stop race conditions from being introduced.
Maintaining separate execution domains for each process structurally eliminates unintended concurrent access to the same shared resources.
Preventing unintended information transfer through shared system resources directly addresses the improper concurrent modification that defines a race condition.
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.
Secure SDLC practices directly require synchronization primitives and concurrency analysis that prevent intra-thread race conditions.
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.
Security testing can detect race conditions through concurrency and stress testing.
Secure development lifecycle includes concurrency and synchronization practices that reduce race conditions.
Application security requirements can mandate thread-safety and locking controls.
Secure architecture principles address concurrent access and resource synchronization.
Secure coding standards directly require proper synchronization primitives to prevent race conditions.
Change management can introduce or remove synchronization flaws during updates.