Skip to main content
VulnerabilityPublished Updated

CVE-2026-0501: SAP S/4HANA Private Cloud and On-Premise (Financials � General Ledger) · SQL Injection

Affects SAP S/4HANA Private Cloud and On-Premise (Financials � General Ledger)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.4% chance of exploitation in 30 days – higher than 41% 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 13 Jan 2026

  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_SESAP S/4HANA Private Cloud and On-Premise (Financials � General Ledger)Affected
  • 103 – 109
7 affected builds
Fixed in–

AI-suggested

To mitigate CVE-2026-0501, organizations should immediately review and restrict user privileges to the minimum necessary, especially for users with access to the Financials General Ledger modules. Implement strict authentication and session management controls to prevent unauthorized access. Monitor database and application logs for unusual or suspicious SQL query patterns indicative of injection attempts. Employ Web Application Firewalls (WAFs) or database activity monitoring tools capable of detecting and blocking anomalous SQL commands. Until SAP releases official patches, consider isolating affected SAP systems from less trusted networks and enforcing network segmentation. Conduct thorough security assessments and penetration testing focused on SQL injection vectors within SAP environments. Once patches are available, apply them promptly following SAP's guidance. Additionally, educate users about the risks of credential compromise and enforce multi-factor authentication to reduce the likelihood of attacker access.

Description

Due to insufficient input validation in SAP S/4HANA Private Cloud and On-Premise (Financials General Ledger), an authenticated user could execute crafted SQL queries to read, modify, and delete backend database data. This leads to a high impact on the confidentiality, integrity, and availability of the application.

References

Community reviews

Loading reviews…