Skip to main content
VulnerabilityPublished Updated

CVE-2025-27429: SAP S/4HANA (Private Cloud) · Code Injection

Affects SAP S/4HANA (Private Cloud)Source CVE Database V5

0

Not known to be exploited · CVSS 9.9 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Apr 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
SAP_SE SAP S/4HANA (Private Cloud)Affected
  • 103 – 108
6 affected builds
Fixed in–

AI-suggested

  1. Immediately review and restrict user privileges to the minimum necessary, especially for users with access to RFC interfaces.
  2. Implement strict monitoring and logging of RFC calls and ABAP code execution to detect anomalous activities indicative of code injection attempts.
  3. Apply SAP security notes and patches as soon as they become available for the affected S/4HANA versions.
  4. Employ network segmentation to limit access to SAP systems and restrict RFC communication to trusted sources only.
  5. Conduct regular security audits and penetration testing focused on SAP environments to identify and remediate potential weaknesses.
  6. Utilize SAP's built-in security tools such as SAP Enterprise Threat Detection to monitor for suspicious behavior.
  7. Educate SAP administrators and developers about secure coding practices and the risks of code injection.
  8. Consider deploying runtime application self-protection (RASP) or web application firewalls (WAF) capable of detecting and blocking code injection patterns targeting SAP interfaces.
  9. 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.

References

Community reviews

Loading reviews…