CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NCVE-2026-109799
High (7.5) in sap se sap cloud sdk for python. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
The SAP Cloud SDK for Python contains an improper cryptographic signature verification vulnerability (CWE-347) in IASContextProvider, the runtime-context provider registered by default via bootstrap(app).IASContextProvider extracted the app_tid, sap_gtid and user_uuid claims from the IAS JWT in the Authorization header using an unverified decoder and wrote them into the request-scoped RuntimeContext without validating the token signature. A remote caller could submit a self-signed JWT naming a victim tenant/user; the forged identity then propagated to every consumer of the runtime context:OTel span attributes (sap.tenancy.tenant_id, user.id) via RuntimeContextSpanProcessorlog records via IdentityLogFilteraudit events (tenant_id, user_initiator_id) via AuditClienttenant routing via CBCClientThis completes an earlier remediation that fixed the same unverified pattern in StarletteIASTelemetryMiddleware but did not cover IASContextProvider.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-347 Improper Verification of Cryptographic Signature
- OWASP Top 10
- A04:2025 Cryptographic Failures
- Published
- Assigned by
- sap (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-109799 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109799?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109799?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-109799 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
- sap_se:sap cloud sdk for python
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| SAP_SE SAP Cloud SDK for Python | < 0.63.1 |
Attack patterns (CAPEC)
- CAPEC-463 Padding Oracle Crypto Attack Severity: High
- CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.