CVE-2026-109799: Improper verification of JWT signature in IASContextProvider leads to tenant/user identity spoofing ( sap-cloud-sdk (pip))

Published Nov 10, 2026
·
Updated

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 apptid, sapgtid and useruuid 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.tenantid, user.id) via RuntimeContextSpanProcessorlog records via IdentityLogFilteraudit events (tenantid, userinitiatorid) via AuditClienttenant routing via CBCClientThis completes an earlier remediation that fixed the same unverified pattern in StarletteIASTelemetryMiddleware but did not cover IASContextProvider.

Affected Software

1 affected component
pypi/sap-cloud-sdk

Event History

Nov 10, 2026
CVE Published
via MITRE·01:04 AM
Data Sourced
via MITRE·01:04 AM
DescriptionSeverity
Data Sourced
via NVD·01:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Are applications using the standard SDK bootstrap exposed?

Yes. IASContextProvider is registered by default through bootstrap(app), so applications using that default runtime-context setup are affected.

2

What does an attacker need to exploit this issue?

A remote caller can submit a self-signed IAS JWT in the Authorization header that names a chosen tenant and user. No privileges or user interaction are indicated by the supplied severity vector.

3

What can be affected after a forged identity is accepted?

The forged tenant and user identity can propagate to OpenTelemetry span attributes, log records, audit events, and tenant routing through CBCClient. This can cause identity spoofing in telemetry, auditing, logging, and routing consumers of the runtime context.

4

Is the earlier StarletteIASTelemetryMiddleware remediation sufficient?

No. The earlier remediation addressed the unverified JWT pattern in StarletteIASTelemetryMiddleware but did not cover IASContextProvider.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203