Skip to content
major vulnerability· requires attention

Affects widely-used SAP NetWeaver ABAP/ABAP Platform; high impact on availability and integrity across enterprises.

ERP

CVE-2026-0509

9.6
Critical
EPSS 0.35%Patch availableFeb 10, 2026

Auth low-priv user can trigger background RFCs without S_RFC authorization.

common questions

Is CVE-2026-0509 being exploited?

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

How severe is CVE-2026-0509?

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

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

What does CVE-2026-0509 affect?

CVE-2026-0509 affects SAP NetWeaver Application Server ABAP, SAP ABAP Platform. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-0509?

Patch SAP notes; enforce S_RFC checks; minimize background RFCs.

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

executive summary
technical analysis
affected
SAP NetWeaver Application Server ABAPSAP ABAP Platform
impact

Privilege escalation via background RFCs; could disrupt service and modify data; no confidentiality impact.

action required

Immediate action required

affected versions
SAP_SE SAP NetWeaver Application Server ABAP and ABAP Platform
  • affectedKRNL64NUC 7.22
  • affected7.22EXT
  • affectedKRNL64UC 7.22
  • affected7.53
  • affectedKERNEL 7.22
  • affected7.54
  • affected7.77
  • affected7.89
  • affected7.93
  • affected9.16
  • affected9.18
  • affected9.19

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