Posted on

SAP OAuth2 Credential Leak: 6 Checks for BTP App Owners

SAP BTP application credential review

SAP discloses critical CVSS 10 flaw in Cloud SDK for Python allowing OAuth2 credential theft, and companies that build custom applications on SAP Business Technology Platform (BTP) should look closely at which SDK version they ship. Tracked as CVE-2026-89111 and published on October 13, 2026, the flaw lets a multi-tenant application send its own OAuth2 client ID and client secret to a server an attacker controls. It works because vulnerable versions of SAP’s official Python client accept any tenant subdomain value and drop it into the token request address. If an attacker can control that subdomain, they can point the request at their own server and capture the credentials, a technique known as server-side request forgery. SAP lists versions below 0.45.2 as affected. Reporting by The Hacker News found later releases, from 0.53.0 to 0.55.0 and the whole 0.36 line, that also lack the check. No attacks have been reported. The practical lesson is that upgrading to “a fixed version” is not enough on its own; teams need to confirm the check exists in the exact build they deploy.

The Six Points to Take Away

  • The flaw leaks the app’s own credentials. The client ID and secret that let your application call BTP services can be sent to an attacker.
  • It needs a controllable tenant subdomain. Multi-tenant apps that pass subdomains into the SDK without validation are the exposed group.
  • Version numbers are misleading here. Some releases after the first fix lack the check again, and no release in the 0.36 line has it.
  • Fixed builds exist. Versions 0.45.2 to 0.52.2 and 0.55.1 to 0.58.4 contain the subdomain check.
  • SAP does not say whether to rotate secrets. The advisory is silent, so the decision is yours.
  • What the secret can do depends on you. The damage from a stolen credential equals the permissions you gave that client.

The checks below turn these points into a short review for any business running Python applications on BTP, whether built in-house or by a partner.

Why the SAP Cloud SDK Flaw Matters to Businesses on BTP

The SAP Cloud SDK flaw matters because OAuth2 client secrets are the keys an application uses to act on your SAP data and services. A leaked secret lets someone call those services as your application, with whatever access you granted it, from anywhere. Unlike a stolen user password, it is rarely protected by multi-factor authentication and often goes unrotated for years.

Many mid-sized companies run custom BTP extensions built by a consulting partner rather than an internal team. In those cases, the business may not know which SDK version is deployed, or that the app is multi-tenant at all. Our team sees this pattern often in cloud environments: the platform is managed by the vendor, the code by a partner, and the credentials by nobody in particular. The shared responsibility model leaves those secrets with you.

A reasonable counterpoint is that exploitation requires the attacker to control the tenant subdomain, which many applications never allow. That is true, and it lowers the risk for single-tenant or tightly controlled apps. It does not remove the need to check, because subdomains often come from onboarding forms, configuration files or partner integrations that nobody has reviewed with this attack in mind.

How the credential leak works

To get an access token, the SDK builds a token address from configuration and inserts the tenant subdomain. Vulnerable builds accept any value, including one that changes the destination host, and then send the client ID and secret to that address.

Why later versions matter

The fix in 0.45.2 added a check that only accepts a simple subdomain of letters, digits and hyphens up to 63 characters. Some later releases, mainly in Destination service calls from 0.53.0 to 0.55.0, lack it again until 0.55.1 restored it in shared token code. Version ranges, not “newer than X”, decide safety.

What a stolen client secret allows

A stolen client secret allows whatever the application’s client is permitted to do on BTP. If that client has broad access to destinations, documents or business data, the exposure is broad too, which is why scope matters as much as the patch.

6 Checks for SAP BTP Application Owners

The six checks below can be run by an internal developer or requested from your SAP partner.

Check 1: Identify every Python app using the SDK

Identifying affected apps is the first check. List every application on BTP that uses SAP Cloud SDK for Python, and note whether each one is multi-tenant. Include apps built and maintained by partners.

Check 2: Confirm the exact SDK version in production

Confirming the deployed version is the second check, because what is in your requirements file may not match what is running. Safe ranges are 0.45.2 to 0.52.2 and 0.55.1 or later. Anything in the 0.36 line, below 0.45.2, or from 0.53.0 to 0.55.0 needs an upgrade, part of a regular patch management process.

Check 3: Validate tenant subdomains before they reach the SDK

Validating subdomains is the third check and SAP’s own advice for apps that cannot upgrade yet. Compare each tenant subdomain against your list of registered tenants before passing it to the SDK, and reject anything else.

Check 4: Rotate client secrets that may have been exposed

Rotating secrets is the fourth check. SAP does not say whether affected apps should replace credentials, so make the call yourself. If an app ran a vulnerable build with attacker-influenced subdomains, treat the secret as exposed and rotate it, since credential theft leaves no trace on your side.

Check 5: Narrow what each client can do

Narrowing client permissions is the fifth check. Apply a least privilege model to service clients so a leaked secret can reach only what that app truly needs.

Check 6: Ask partners how they track SDK advisories

Asking partners is the sixth check. Find out how your SAP partner learns about SDK flaws and how fast they patch, and add that answer to your vendor risk management records.

How to Keep Third-Party SDKs From Becoming Blind Spots

Keeping SDKs from becoming blind spots means treating them like any other software you depend on.

Track dependencies with a software bill of materials

A software bill of materials lists every library inside an application, which turns “are we affected?” into a search. It is a basic defense against supply chain attacks.

Test multi-tenant input handling

Include tenant and subdomain handling in application penetration testing, since input that shapes a network request is a common source of request forgery flaws.

Plan for a leaked service credential

Add a leaked service credential to your incident response plan, covering who rotates it, who reviews its recent use and who tells affected customers.

Frequently Asked Questions

What is CVE-2026-89111?

CVE-2026-89111 is a CVSS 10.0 flaw in SAP Cloud SDK for Python that can send a multi-tenant application’s OAuth2 client credentials to an attacker-controlled server when the attacker controls the tenant subdomain.

Which SAP Cloud SDK versions are safe?

Versions 0.45.2 to 0.52.2 and 0.55.1 to 0.58.4 contain the subdomain check. The 0.36 line, versions below 0.45.2 and releases from 0.53.0 to 0.55.0 lack it in some code paths.

Has this SAP flaw been exploited?

No attacks had been reported when SAP published its advisory on October 13, 2026.

Should we rotate our OAuth2 client secret?

SAP’s advisory does not say. If an affected app may have received attacker-controlled subdomains, rotating the secret is the safer choice.

What if we cannot upgrade right away?

Compare each tenant subdomain against your list of registered tenants before passing it to the SDK, as SAP recommends, and plan the upgrade promptly.

Who Is Behind This Advice

This guidance comes from the cloud and security teams at Mindcore Technologies, who help small and midsize businesses secure cloud platforms, custom applications and the credentials that connect them. The six checks above reflect the review we would run for a client with custom applications on SAP BTP. Our role is to give your team and your partners a clear checklist, so decisions about your systems stay with you. Mindcore is led by CEO Matt Rosenthal, who focuses on helping growing businesses close the gaps between the vendor, the partner and the people who own the data.

Verify the Build, Not Just the Version

The SAP Cloud SDK flaw is a reminder that a fix can be undone by a later release, and that a client secret is only as safe as the code that handles it. Identify every Python app on BTP, confirm the exact SDK version in production, validate tenant subdomains, rotate any secret that may have been exposed and narrow what each client can do. Ask partners how they track advisories, keep a bill of materials and test multi-tenant input handling. If you want help reviewing your SAP and cloud application credentials, book a free strategy call and our team will walk through it with you.

Related Posts

Matt Rosenthal