Skip to content
major vulnerability· requires attention

Widely deployed SAP S/4HANA ERP; admin rights allow backdoor via RFC, risking full system compromise.

ERP

CVE-2026-0498

9.1
Critical
EPSS 0.47%Patch availableJan 13, 2026

Admin-authenticated ABAP/OS command injection via SAP RFC module.

common questions

Is CVE-2026-0498 being exploited?

Not confirmed. CVE-2026-0498 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-0498?

CVE-2026-0498 is rated Critical with a CVSS score of 9.1. 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-0498?

Yes. A fix has been recorded for CVE-2026-0498. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-0498 affect?

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

What should I do about CVE-2026-0498?

Patch ASAP when available; restrict RFC/admin access; review ABAP 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 CloudSAP S/4HANA On-Premise
impact

Allows admin to inject ABAP/OS commands through RFC, bypassing checks, enabling full system compromise.

action required

Immediate action required

affected versions
SAP_SE SAP S/4HANA (Private Cloud and On-Premise)
  • 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