Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-89111 Overview
CVE-2026-89111 is a Server-Side Request Forgery (SSRF) vulnerability in the SAP Cloud SDK for Python affecting multi-tenant Business Technology Platform (BTP) applications. The flaw resides in the OAuth2 token acquisition flow, where the tenant_subdomain parameter is incorporated into the authorization server URL without proper validation. An attacker who controls this parameter can redirect OAuth2 token requests to an attacker-controlled server. The redirected requests carry client credentials, which the attacker can then exfiltrate and reuse against legitimate SAP BTP services. The vulnerability is tracked under CWE-918.
Critical Impact
Unauthenticated network attackers can exfiltrate OAuth2 client credentials from multi-tenant BTP applications, enabling full impersonation of the compromised tenant.
Affected Products
- SAP Cloud SDK for Python
- Multi-tenant SAP Business Technology Platform (BTP) applications built on the SDK
- OAuth2 token acquisition flows that accept a tenant_subdomain input
Discovery Timeline
- 2026-10-13 - CVE-2026-89111 published to the National Vulnerability Database
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-89111
Vulnerability Analysis
The SAP Cloud SDK for Python builds OAuth2 token endpoint URLs dynamically for each tenant. The SDK uses the tenant_subdomain value to construct the hostname of the authorization server before requesting an access token. When the SDK accepts this value from untrusted input without validating the resulting target, the request can be redirected to any host the attacker chooses.
Multi-tenant BTP applications typically pass the subdomain from HTTP request context, such as a header or JWT claim, into the SDK. An attacker who manipulates that input triggers an outbound HTTPS request from the application to an attacker-controlled endpoint. That request carries OAuth2 client credentials used to authenticate the application against the SAP XSUAA service.
Once credentials reach the attacker, they can be used to request legitimate access tokens for the tenant. The attacker then calls BTP APIs as the application identity, bypassing tenant isolation. The scope change in the CVSS vector reflects this cross-tenant impact.
Root Cause
The root cause is insufficient validation of the tenant_subdomain parameter prior to its use in URL construction. The SDK trusts the subdomain string and concatenates it into the authorization server URL. No allowlist, format check, or confirmation against the trusted XSUAA domain is enforced before the credential-bearing request leaves the application.
Attack Vector
The attack vector is network based and requires no authentication or user interaction. An attacker sends a crafted request to a vulnerable BTP application. The request includes a tenant_subdomain value that resolves to an attacker-controlled host. The application invokes the SDK, which issues an OAuth2 token request to that host. The attacker captures the submitted client_id and client_secret. For technical details and vendor remediation guidance, see the GitHub Security Advisory and the SAP Security Patch Day notice.
Detection Methods for CVE-2026-89111
Indicators of Compromise
- Outbound HTTPS connections from BTP application workloads to hosts outside the expected *.authentication.<region>.hana.ondemand.com XSUAA domain.
- OAuth2 token requests containing unusual or externally resolvable tenant_subdomain values in application logs.
- Successful XSUAA token issuance from source IPs or user agents that differ from the application's normal egress profile.
Detection Strategies
- Inspect application and reverse-proxy logs for tenant_subdomain values that contain dots, slashes, URL-encoded characters, or non-tenant hostnames.
- Correlate SDK HTTP client logs with outbound firewall telemetry to identify token requests sent to non-SAP destinations.
- Alert on any SAP BTP OAuth2 client credential appearing in authentication events from unexpected network locations.
Monitoring Recommendations
- Enable egress logging on all BTP workloads and baseline the authorized set of XSUAA token endpoints per region.
- Forward application, SDK, and egress logs into a central analytics platform and build detections keyed on destination host of OAuth2 requests.
- Monitor XSUAA audit events for credential use that does not correlate with legitimate application activity.
How to Mitigate CVE-2026-89111
Immediate Actions Required
- Upgrade the SAP Cloud SDK for Python to the fixed release identified in the GitHub Security Advisory.
- Rotate all OAuth2 client credentials for BTP applications that may have processed untrusted tenant_subdomain input.
- Review XSUAA token issuance logs for the last 90 days for anomalous activity tied to affected service bindings.
Patch Information
SAP has published remediation details via the SAP Security Patch Day process. Apply the fixed version of the SAP Cloud SDK for Python as listed in the vendor advisory and redeploy all affected BTP applications. Confirm that transitive dependencies and container images bundling the SDK are rebuilt against the patched version.
Workarounds
- Validate tenant_subdomain against a strict allowlist of known tenant identifiers before passing it to the SDK.
- Restrict application egress with network policies that permit outbound HTTPS only to the expected XSUAA hostnames for the deployment region.
- Short-lived credential rotation and binding-level secrets reduce the exposure window if exfiltration occurs.
# Example egress restriction concept for a BTP workload (illustrative)
# Allow outbound only to the regional XSUAA authorization server
ALLOWED_XSUAA_HOST="authentication.eu10.hana.ondemand.com"
# Validate tenant subdomain against an allowlist before SDK calls
grep -E "^[a-z0-9][a-z0-9-]{1,61}[a-z0-9]$" tenants.allowlist
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

