SAP patches a 10-out-of-10 flaw that can send AI agents' credentials to attackers; earnings due October 21

One URL parameter carried the keys

SAP's▲+0.14% — SAP, up 0.14 percent today October patch day shipped 22 new and updated security notes on October 13, 2026, four of them rated critical ¹. The worst is CVE-2026-89111, a server-side request forgery scored 10.0↗ out of 10 on the standard severity scale, fixed in version 0.45.2 of the Cloud SDK for Python, SAP's official toolkit for building AI agents and Python applications on its Business Technology Platform cloud ¹²⁴.

The SDK takes a value called tenant_subdomain to name the customer a request belongs to. Hand it a crafted value and the SDK builds its token request around that value, sending the application's OAuth2 client ID and secret↗, the standing credentials software uses to authenticate on SAP's cloud, to a server the attacker controls ². No login, no privileges and no user trickery are needed ³.

The timing lands on money. SAP trades at 28.6 times earnings, the stock at $220.10 against a $264.71 average analyst target, and reports third-quarter results after the close on October 21: consensus $2.04 a share on $11.45 billion of revenue↗, after July's quarter missed at $1.82 against a $2.00 estimate ⁵.

The fix shipped in August and slipped back in September

The validation check that blocks crafted subdomains first arrived on August 21, in version 0.45.2, listed under bug fixes with no mention of security; the advisory followed 53 days later ⁶. Until that release, no version of the SDK had the check ⁶.

Six releases published between September 10 and 18, versions 0.53.0 through 0.55.0, moved token handling for the Destination service module onto new shared code that skipped the check ⁶. Two releases on the older 0.36 line, published after the August fix, never had it ⁶.

The advisory lists nothing above 0.45.2 as affected, and neither it nor the release notes say whether the six September releases fall under this CVE, or whether applications that ran them should replace their credentials ⁶. The newest release, 0.58.4, passes all eleven of SAP's own tests ⁶.

SAP's worst bugs get used within days

The patch matters because SAP's recent criticals do not stay theoretical. August's maximum-severity flaw in Commerce Cloud was flagged as actively exploited days after its fix↗ ⁴. September's CVE-2026-44756 sat exposed on more than 10,000 internet-facing systems by the count of Onapsis, the security firm that reported it ⁴. CISA, the US cyber agency, holds 14 SAP flaws in its exploited-vulnerabilities catalog dating to November 2021, three tied to ransomware ⁴.

The premium the flaw lands on

Underneath the security noise, the business keeps compounding: revenue has beaten its year-ago quarter for twelve straight quarters, $11.2 billion in the June quarter ⁷. The next reading arrives with the October 21 earnings report, where analysts expect $11.45 billion ⁵.

No attacks named yet, and October 21 prices the premium

No exploitation of the new flaw is confirmed, and it is not on CISA's catalog ⁸. SAP shipped a patch and a workaround↗, an allowlist of registered tenant subdomains ². The bull case leans on 26 percent growth in current cloud backlog, cloud contracts signed but not yet booked as revenue, and on Joule, SAP's AI assistant, reported to lift productivity by up to 20 percent ⁵. Neither number takes back a credential already delivered to the wrong server.

The advisory leaves the decision to replace possibly exposed credentials to each customer ⁶. Any application still running an unfixed release can have its agent's credentials sent to an attacker's server by one crafted parameter ². The stock already traded 27 percent below its peak in September, on doubts about the AI roadmap, with a buyback running underneath ⁹.

Two readings settle the week: whether CVE-2026-89111 is used within days of its fix, as August's Commerce Cloud flaw was, and whether the October 21 earnings report shows cloud revenue carrying the premium ⁴.