CVE-2025-27429: SAP S/4HANA (Private Cloud) · Code Injection
Affects SAP S/4HANA (Private Cloud)Source CVE Database V5
Not known to be exploited · CVSS 9.9 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 56% 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 8 Apr 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAP_SE SAP S/4HANA (Private Cloud) | Affected
| Fixed in– |
AI-suggested
- Immediately review and restrict user privileges to the minimum necessary, especially for users with access to RFC interfaces.
- Implement strict monitoring and logging of RFC calls and ABAP code execution to detect anomalous activities indicative of code injection attempts.
- Apply SAP security notes and patches as soon as they become available for the affected S/4HANA versions.
- Employ network segmentation to limit access to SAP systems and restrict RFC communication to trusted sources only.
- Conduct regular security audits and penetration testing focused on SAP environments to identify and remediate potential weaknesses.
- Utilize SAP's built-in security tools such as SAP Enterprise Threat Detection to monitor for suspicious behavior.
- Educate SAP administrators and developers about secure coding practices and the risks of code injection.
- Consider deploying runtime application self-protection (RASP) or web application firewalls (WAF) capable of detecting and blocking code injection patterns targeting SAP interfaces.
- Maintain an incident response plan tailored for SAP system compromises to enable rapid containment and recovery.
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.