Skip to content
major vulnerability· requires attention

Affects widely deployed SAP ERP/CRM; authenticated SQL execution can compromise the entire database (high-impact, critical).

ERP

CVE-2026-0488

9.9
Critical
EPSS 0.51%Patch availableFeb 10, 2026

Authenticated SAP CRM/SAP S/4HANA flaw allows arbitrary SQL; full DB compromise.

common questions

Is CVE-2026-0488 being exploited?

Not confirmed. CVE-2026-0488 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.51% probability of exploitation in the next 30 days.

How severe is CVE-2026-0488?

CVE-2026-0488 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-0488?

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

What does CVE-2026-0488 affect?

CVE-2026-0488 affects SAP CRM, SAP S/4HANA, Scripting Editor. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-0488?

Apply SAP patches; restrict scripting editor access; monitor SQL activity.

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

executive summary
technical analysis
affected
SAP CRMSAP S/4HANAScripting Editor
impact

Authenticated attacker can execute arbitrary SQL via a function module in SAP S/4HANA/Scripting Editor, risking full DB compromise.

action required

Patch when available

affected versions
SAP_SE SAP CRM and SAP S/4HANA (Scripting Editor)
  • affectedS4FND 102
  • affected103
  • affected104
  • affected105
  • affected106
  • affected107
  • affected108
  • affected109
  • affectedSAP_ABA 700
  • affectedWEBCUIF 700
  • affected701
  • affected730
  • affected731
  • affected746
  • affected747
  • affected748
  • affected800
  • affected801

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