CVE-2026-109799: SAP Cloud SDK for Python · Improper Verification of Cryptographic Signature
Affects SAP Cloud SDK for PythonSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 0.63.1 soon.
Data as of 10 Nov 2026, 01:47 UTC
Thin evidence
One scorer or none| CNA (sap) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 0.63.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade SAP Cloud SDK for Python to 0.63.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SAP_SESAP Cloud SDK for Python | Affected
| Fixed in
|
AI-suggested
Upgrade SAP Cloud SDK for Python to version 0.63.1 or later, where the improper signature verification in IASContextProvider is fixed. No other mitigation is required as the vendor has provided an official fix.
Description
CVE-2026-109799 is a high-severity vulnerability in SAP Cloud SDK for Python versions prior to 0.63.1. It involves improper verification of cryptographic signatures in the IASContextProvider component, which extracts claims from JWT tokens without validating their signatures. This flaw allows remote attackers to submit self-signed JWTs with forged tenant and user identities, causing these forged identities to propagate to various runtime context consumers such as telemetry, logs, audit events, and tenant routing. The issue was fixed in version 0.63.1.