CVE-2025-42957: SAP S/4HANA (Private Cloud or On-Premise) · Improper Control of Generation of Code
Affects SAP S/4HANA (Private Cloud or On-Premise)Source CVE Database V5
Not known to be exploited · CVSS 9.9 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.6% chance of exploitation in 30 days – higher than 76% 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:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2025
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_SE SAP S/4HANA (Private Cloud or On-Premise) | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-42957, organizations should immediately audit and restrict user privileges, ensuring that only trusted users have access to RFC interfaces and function modules. Implement strict access controls and network segmentation to limit exposure of SAP RFC endpoints to untrusted networks. Monitor SAP system logs and ABAP code execution for unusual or unauthorized activity indicative of code injection attempts. Employ SAP's security notes and advisories as soon as patches or official mitigations become available. Until patches are released, consider disabling or restricting the vulnerable function modules if feasible, or applying SAP recommended temporary workarounds. Conduct thorough penetration testing and vulnerability assessments focused on SAP environments to identify potential exploitation paths. Enhance incident response readiness by preparing playbooks specific to SAP code injection and unauthorized access scenarios. Regularly update and harden SAP systems following best practices, including applying the principle of least privilege and continuous monitoring of SAP user activities.
Description
SAP S/4HANA allows an attacker with user privileges to exploit a vulnerability in the function module exposed via RFC. This flaw enables the injection of arbitrary ABAP code into the system, bypassing essential authorization checks. This vulnerability effectively functions as a backdoor, creating the risk of full system compromise, undermining the confidentiality, integrity and availability of the system.