CVE-2026-23689: SAP Supply Chain Management · Unchecked Input for Loop Condition
Affects SAP Supply Chain ManagementSource CVE Database V5
Not known to be exploited · CVSS 7.7 High.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAP_SESAP Supply Chain Management | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-23689, organizations should first verify if their SAP SCM installations are running affected versions (SCMAPO 713, 714, SCM 700-702, 712). Since no patches are currently linked, immediate mitigations include: 1) Restricting network access to the vulnerable remote-enabled function modules by applying strict access controls and network segmentation to limit exposure only to trusted users and systems. 2) Implementing monitoring and alerting for abnormal invocation patterns or unusually large loop-control parameter values to detect potential exploitation attempts early. 3) Enforcing least privilege principles to reduce the number of users with access to invoke the vulnerable function modules. 4) Collaborating with SAP support for any available interim fixes or workarounds and applying them promptly once released. 5) Conducting regular audits of user accounts and session activities to identify compromised credentials that could be used to exploit this vulnerability. 6) Considering deployment of runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious parameter values targeting the vulnerable functions.
Description
Due to an uncontrolled resource consumption (Denial of Service) vulnerability, an authenticated attacker with regular user privileges and network access can repeatedly invoke a remote-enabled function module with an excessively large loop-control parameter. This triggers prolonged loop execution that consumes excessive system resources, potentially rendering the system unavailable. Successful exploitation results in a denial-of-service condition that impacts availability, while confidentiality and integrity remain unaffected.