Affects SAP Fiori ERP, a widely deployed enterprise app; privilege escalation could disrupt operations and expose data.
CVE-2026-0511
Privilege escalation in SAP Fiori Intercompany Balance Reconciliation due to missing auth checks.
Is CVE-2026-0511 being exploited?
Not confirmed. CVE-2026-0511 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.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-0511?
CVE-2026-0511 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-0511?
Not known from our data. No patch reference has been recorded for CVE-2026-0511, 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-0511 affect?
CVE-2026-0511 affects SAP Fiori Intercompany Balance Reconciliation, SAP Fiori. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-0511?
Apply SAP security note/patch when available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated user can escalate privileges in SAP Fiori App, exposing data and compromising integrity; availability not impacted.
Patch when possible
- affectedUIAPFI70 500
- affected600
- affected700
- affected800
- affected900
- affected901
- affected902
- affectedS4CORE 102
- affected103
- affected104
- affected105
- affected106
- affected107
- affected108
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.