SAP ABAP is widely deployed; authenticated RFC access can affect many customers; impacts core data integrity and system availability.
CVE-2026-0506
Authenticated RFC abuse can execute FORMs; modify data and trigger actions.
Is CVE-2026-0506 being exploited?
Not confirmed. CVE-2026-0506 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-0506?
CVE-2026-0506 is rated High with a CVSS score of 8.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-0506?
Yes. A fix has been recorded for CVE-2026-0506. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-0506 affect?
CVE-2026-0506 affects SAP ABAP Application Server, SAP ABAP Platform. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-0506?
Apply SAP security notes and restrict RFC access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Data integrity and availability risk: authenticated user can modify data via FORMs and invoke system functionality.
Patch when possible
- affectedSAP_BASIS 700
- affectedSAP_BASIS 701
- affectedSAP_BASIS 702
- affectedSAP_BASIS 731
- affectedSAP_BASIS 740
- affectedSAP_BASIS 750
- affectedSAP_BASIS 751
- affectedSAP_BASIS 752
- affectedSAP_BASIS 753
- affectedSAP_BASIS 754
- affectedSAP_BASIS 755
- affectedSAP_BASIS 756
- affectedSAP_BASIS 757
- affectedSAP_BASIS 758
- affectedSAP_BASIS 816
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.