Skip to content
major vulnerability· requires attention

ERP core SAP S/4HANA vulnerability could disrupt multiple enterprises; widely deployed.

ERP

CVE-2026-0501

9.9
Critical
EPSS 0.47%Jan 13, 2026

Auth user can inject SQL in SAP S/4HANA Ledger via input validation flaw.

common questions

Is CVE-2026-0501 being exploited?

Not confirmed. CVE-2026-0501 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.

How severe is CVE-2026-0501?

CVE-2026-0501 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-0501?

Not known from our data. No patch reference has been recorded for CVE-2026-0501, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-0501 affect?

CVE-2026-0501 affects SAP S/4HANA Private Cloud (Financials General Ledger), SAP S/4HANA On-Premise (Financials General Ledger). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-0501?

Patch SAP fix; enforce input validation; restrict access to General Ledger modules.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
SAP S/4HANA Private Cloud (Financials General Ledger)SAP S/4HANA On-Premise (Financials General Ledger)
impact

Authenticated user can inject SQL to read/modify/delete backend data; compromises confidentiality, integrity, and availability.

action required

Immediate action required

affected versions
SAP_SE SAP S/4HANA Private Cloud and On-Premise (Financials � General Ledger)
  • affectedS4CORE 102
  • affected103
  • affected104
  • affected105
  • affected106
  • affected107
  • affected108
  • affected109

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free