Skip to main content

SAP Approuter CVE-2026-58239

| EUVDEUVD-2026-55871 LOW
Reliance on Untrusted Inputs in a Security Decision (CWE-807)
2026-08-11 sap GHSA-w69g-xj7m-rmrv
3.7
CVSS 3.1 · Vendor: sap
View

Attack ChainAIDerived

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

  1. Access
    Identify public SAP Approuter BTP endpoint
  2. Exploit
    Craft HTTP request with spoofed tenant context attribute
  3. Execution
    Submit request under favorable uncontrolled conditions
  4. Impact
    Receive partial cross-tenant data in response

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Trusted input validation
Exploitation Conditions

The attacker must have network access to the SAP Approuter HTTP endpoint (AV:N); no authentication is required to send the crafted request (PR:N per vendor CVSS). The decisive limiting condition is High Attack Complexity (AC:H): the description states that exploitation succeeds only 'under conditions not fully within their control,' meaning some external state - such as a specific routing configuration, race condition, or backend processing state - must be present that the attacker cannot reliably engineer. The vulnerability is relevant only in multi-tenant deployments; single-tenant Approuter instances have no second tenant whose context could be spoofed. Affected deployments must be running the SAP Approuter node.js package below version 23.0.0. No user interaction is required (UI:N), and no special platform or operating system dependency has been identified beyond the node.js runtime.

Impact

The vendor CVSS base score of 3.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) is low and reflects an accurate picture of constrained real-world risk. The AC:H metric is the dominant limiting factor: the description explicitly states exploitation occurs 'under conditions not fully within their control,' indicating that reliable, on-demand triggering is not possible. No EPSS data was provided in available intelligence; given the AC:H rating and absence of KEV listing or known public exploit code, EPSS probability is expected to be low. There is no CISA KEV listing and no public proof-of-concept identified at time of analysis. SSVC signals suggest exploitation status is unreported, automatable is no (due to AC:H), and technical impact is partial. Despite the low score, organizations subject to data residency or tenant isolation compliance requirements (e.g., GDPR, SOC 2, HIPAA on BTP) should treat this as a patch-cycle priority rather than an emergency, since even low-probability cross-tenant disclosure can constitute a reportable data exposure event.

Exploit ScenarioDerived

An unauthenticated attacker identifies a public-facing SAP BTP application endpoint served by a vulnerable SAP Approuter instance and crafts HTTP requests containing manipulated tenant context identifiers - such as forged headers or modified URL components - designed to assert a different tenant's identity. When specific internal conditions align that are not fully under the attacker's control (per AC:H), the Approuter accepts the spoofed context and returns a partial response containing the targeted tenant's data. No public exploit code has been identified at time of analysis.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Aug 11, 2026

Tenant context spoofing in SAP Approuter (node.js package < 23.0.0) allows unauthenticated remote attackers to craft requests that bypass tenant isolation, resulting in limited cross-tenant information disclosure. Exploitation is constrained by High Attack Complexity (AC:H per vendor CVSS), meaning conditions necessary for success are not fully under attacker control. No public exploit has been identified at time of analysis and a vendor patch is available, making this a low-urgency but compliance-relevant issue for SAP BTP multi-tenant deployments.

RemediationAI

The primary remediation is to upgrade the SAP Approuter node.js package to version 23.0.0 or later, as confirmed by vendor advisory SAP Security Note 3786038 and EUVD-2026-55871. Administrators should consult https://me.sap.com/notes/3786038 for deployment instructions and https://url.sap/sapsecuritypatchday for the broader patch-day context. If immediate patching is not feasible, a compensating control is to deploy a WAF or API gateway upstream of the Approuter configured to validate and normalize tenant-identifying request attributes (headers, URL segments, or query parameters) before they reach the package - though this requires knowing which specific inputs are exploited, and misconfiguration could disrupt legitimate multi-tenant routing. Restricting Approuter endpoints to known IP ranges reduces external attack surface but is often impractical for public-facing BTP applications. Neither workaround substitutes for the vendor patch given the nature of the CWE-807 root cause.

Affected VersionsENISA

SAP Business AI Platform (Approuter) SAP Approuter node.js package < 23.0.0

Affected Packages

euvd sap_business_ai_platform_approuter_sap_approuter_node_js_package fix: 23.0.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

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

Technical ContextAI · show details

SAP Approuter is a node.js package that acts as the central reverse-proxy and routing layer for applications hosted on SAP Business Technology Platform (BTP), handling authentication, authorization, and - critically for SaaS deployments - tenant context resolution. In multi-tenant architectures, the Approuter identifies the requesting tenant from inbound request attributes (headers, URL subdomains, or query parameters) and enforces data isolation accordingly. The root cause is CWE-807 (Reliance on Untrusted Inputs in a Security Decision): the Approuter incorporates attacker-supplied input into its tenant-context determination without sufficient validation, allowing a crafted request to assert a false tenant identity. The affected component is precisely identified by CPE cpe:2.3:a:sap_se:sap_business_ai_platform_(approuter):*:*:*:*:*:*:*:*, covering all versions of the package prior to 23.0.0.

Know when Sap Business Ai Platform Approuter 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 3.7 LOW
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 3.7 LOW

Network-accessible endpoint, no auth needed, but uncontrollable exploitation conditions justify AC:H; only partial cross-tenant confidentiality impact with no integrity or availability effect.

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

Primary rating from Vendor (sap).

CVSS VectorVendor: sap

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

Lifecycle Timeline

1
Patch available
Aug 11, 2026 - 01:02 EUVD

DescriptionCVE.org

SAP Approuter does not sufficiently validate tenant context in inbound requests. An unauthenticated attacker could send specially crafted requests to spoof the tenant context under conditions not fully within their control. Successful exploitation could allow limited access to another tenant's information, resulting in a low impact on confidentiality. There is no impact on integrity and availability.

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
Medium
core routing package for SAP BTP multi-tenant enterprise applications
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 LOW
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.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· derived
Defer
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

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

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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