Skip to main content

SAP ABAP Platform CVE-2026-89120

| EUVDEUVD-2026-98199 HIGH
Initialization of a Resource with an Insecure Default (CWE-1188)
2026-10-13 sap GHSA-hxp9-cq3v-3qr5
7.1
CVSS 3.1 · Vendor: sap
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged SAP user
  2. Delivery
    Access session manager via FLP
  3. Exploit
    Send crafted request opening single transaction mode
  4. Execution
    Bypass authorization restrictions
  5. Impact
    Tamper with restricted data/functionality

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V13 - Configuration Secure default settings
Exploitation Conditions

Exploitation requires an authenticated low-privileged SAP account (CVSS PR:L) and that the session manager be reachable such that it can be opened in single transaction mode - including via the Fiori Launchpad (FLP), so environments exposing FLP to a broad low-privilege user base are most at risk. The condition is specifically this regression: a SAP API change reintroduced the previously fixed authorization weakness, so only SAP ABAP Platform versions carrying that regressed API (not yet patched per SAP Note 3626303) are exploitable. Limiting factors: valid credentials are mandatory (no anonymous/pre-auth path), no availability impact is possible, and confidentiality exposure is low - the realistic blast radius is unauthorized integrity-affecting actions, not data theft or outage.

Impact

This is a moderate-priority, authenticated issue rather than a drop-everything emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N = 7.1 High) indicates network-reachable, low-complexity exploitation, but PR:L confirms the attacker must already hold a low-privileged, authenticated SAP account - so this is a privilege-escalation/authorization-bypass primitive for an insider or a credential-holding adversary, not a pre-auth internet mass-exploitation bug. The primary damage is to integrity (I:H): the restriction bypass lets the attacker reach functionality or data manipulation they should be blocked from, with only low confidentiality exposure (C:L) and no availability impact (A:N). No EPSS score was supplied, the CVE is not listed in CISA KEV, and no public POC is referenced, so exploitation status is: no public exploit identified at time of analysis. Notably this is a REGRESSION - SAP states a prior fix was undone by an API change reintroducing a known authorization weakness (CWE-1188), which raises the practical likelihood that exploitation techniques for the original flaw may already be understood by researchers even though no current POC is published. Net: a real patch-cycle priority for SAP shops (especially where Fiori Launchpad/FLP is broadly exposed to many low-privilege users), but the authentication requirement and lack of KEV/EPSS/POC signals argue against treating it as an active widespread-exploitation event.

Exploit ScenarioDerived

A low-privileged authenticated SAP user (or an attacker who has phished/obtained such credentials) sends specially crafted requests that open the session manager in single transaction mode - reachable including from the Fiori Launchpad - to bypass authorization restrictions and perform integrity-impacting actions they should not be permitted. No public exploit code is currently identified, and because the flaw is a regression of a previously fixed weakness, the exploitation approach for the original issue may be a useful starting point for an attacker.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

An authorization bypass in SAP ABAP Platform lets a low-privileged, authenticated user open the session manager in single transaction mode - including through the Fiori Launchpad (FLP) - and then send crafted requests that defeat restrictions the platform had previously enforced correctly. The weakness is a regression: an underlying SAP API change reintroduced a flaw that had already been fixed, so only ABAP Platform deployments carrying that regressed API (and not yet covered by SAP Note 3626303) are exposed. Impact is rated 7.1 with high integrity and low confidentiality consequences and no availability impact (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N); valid low-privilege credentials are mandatory, so this is an authenticated privilege-escalation-style issue rather than a pre-auth intrusion path, and no public exploit identified at time of analysis.

RemediationAI

Apply the vendor fix referenced by SAP Note 3626303 (https://me.sap.com/notes/3626303), which is the authoritative correction for this regression; because the flaw is a regressed API default rather than a bug in a single binary, the note should be used to confirm whether your ABAP Platform level is in scope and to obtain the specific patch/support-package level, with SAP Security Patch Day (https://url.sap/sapsecuritypatchday) as the tracking source - patch available per vendor advisory, and the exact fixed version is not stated in the available data, so verify against the note before assuming a given support package is remediated. If immediate patching is not possible, the following compensating controls are actionable but carry trade-offs: restrict which user groups can reach the Fiori Launchpad at all (via role assignment and network/reverse-proxy ACLs) to shrink the low-privilege population able to open the session manager, accepting that legitimate business users will lose FLP access and require alternative UI paths; disable or block the single transaction mode entry point for non-administrative roles through transactional authorization objects where the platform allows it, accepting that some power users will lose a productivity feature; and log and alert on session-manager invocations in single transaction mode from low-privileged accounts to detect attempted abuse, accepting that this is detection rather than prevention and relies on adequate log retention and monitoring coverage. Note that since exploitation requires only valid low-privilege credentials, credential hygiene and prompt deactivation of unused accounts reduce but do not eliminate exposure, and no vendor-released workaround substitute for the note-level fix is identified in the provided data.

Affected VersionsENISA

SAP ABAP Platform 9.16
SAP ABAP Platform KERNEL 7.93

Affected Packages

euvd sap_abap_platform no fix
euvd sap_abap_platform_kernel no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

SAP ABAP Platform is SAP's core application server runtime, hosting ABAP-based business applications and, through the Fiori Launchpad, the browser-facing entry point for most modern SAP user interaction. The session manager governs user session state and is normally constrained so that privileged administrative or cross-transaction operations are not reachable from an ordinary low-privileged session; opening it in single transaction mode was previously restricted because that mode otherwise allows a user to chain behaviour across transactions in a way that skips authorization checks. This CVE is tracked under CWE-1188 (Insecure Default Initialization of Resource): a change to an SAP API reset the default state of the session-manager resource to a permissive configuration rather than the hardened setting shipped by the earlier fix, re-opening a previously closed authorization gap. Because the regression is in the API contract rather than in an isolated component, any ABAP stack that pulled in the affected API level inherits the weakened default, which is why the CPE entry covers the ABAP Platform generically (cpe:2.3:a:sap_se:sap_abap_platform:*:*:*:*:*:*:*:*) instead of a narrow version string. The attack surface is the FLP-reachable session manager: a low-privileged authenticated user invokes it in single transaction mode and uses crafted requests to perform actions their authorization profile should deny. Confidentiality exposure is limited (C:L) because the bypass primarily enables state-changing operations, while availability is unaffected (A:N) since the technique does not disable or crash the session service.

Know when Sap Abap Platform gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (sap) PRIMARY 7.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
vuln.today AI 7.1 HIGH

Network-reachable via FLP (AV:N/AC:L), but requires a low-privileged authenticated account (PR:L); authorization bypass chiefly corrupts restricted data (I:H) with minor info exposure (C:L) and no availability effect.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (sap).

CVSS VectorVendor: sap

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

DescriptionCVE.org

A regression caused by an API change in SAP ABAP Platform reintroduces a previously fixed authorization weakness. The session manager can be opened in single transaction mode, including from FLP. A low-privileged attacker could exploit this to bypass restrictions via specially crafted requests, resulting in high impact on integrity and low impact on confidentiality. There is no impact on availability.

Executive ViewAI

Why It Matters

A regression in the SAP ABAP Platform API allows users who already hold valid low-privilege credentials to bypass authorization restrictions in the session manager - including through the Fiori Launchpad - and modify data they should not be able to change. Because the flaw sits in the core ABAP platform that underpins most SAP business applications, any organization running affected deployments carries integrity risk across business-critical processes, while confidentiality impact is low and availability is unaffected. No vendor-released patch is identified at this time and no public exploit has been identified, so leadership should treat this as a managed containment risk in which the realistic threat is an insider or a compromised low-privilege account rather than an external mass-exploitation event.

Business Impact: High
Compensating Controls

Interim mitigations: restrict session-manager single transaction mode and Fiori Launchpad access to least-privilege users; remove excessive authorizations from low-privilege accounts; enforce MFA and strong credential hygiene (valid low-privilege credentials are required, and access is authenticated); apply the vendor guidance in SAP Note 3626303 where it covers your deployment; enable session and FLP audit logging with alerting on crafted-request patterns; and limit network reachability of the ABAP Platform to trusted segments. No vendor-released patch identified at time of analysis.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
High
SAP ABAP Platform underpins core SAP ERP across large enterprises
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy