Vulnerability in ghcr.io/open-webui/pipelines:main
CVE ID CVE-2026-35030
CVE score 9.100000381469727
Affected package version litellm.1.72.6
Fixed package version litellm.1.83
Impact
When JWT authentication is enabled (enable_jwt_auth: true ), the OIDC userinfo cache uses token[:20] as the cache key. JWT headers produced by the same signing algorithm generate identical first 20 characters.
This configuration option is not enabled by default. Most instances are not affected.
An unauthenticated attacker can craft a token whose first 20 characters match a legitimate user’s cached token. On cache hit, the attacker inherits the legitimate user’s identity and permissions. This affects deployments with JWT/OIDC authentication enabled.
Patches
Fixed in v1.83.0. The cache key now uses the full hash of the JWT token.
Vulnerability in ghcr.io/open-webui/pipelines:main
CVE ID CVE-2026-35030
CVE score 9.100000381469727
Affected package version litellm.1.72.6
Fixed package version litellm.1.83
Impact
When JWT authentication is enabled (enable_jwt_auth: true ), the OIDC userinfo cache uses token[:20] as the cache key. JWT headers produced by the same signing algorithm generate identical first 20 characters.
This configuration option is not enabled by default. Most instances are not affected.
An unauthenticated attacker can craft a token whose first 20 characters match a legitimate user’s cached token. On cache hit, the attacker inherits the legitimate user’s identity and permissions. This affects deployments with JWT/OIDC authentication enabled.
Patches
Fixed in v1.83.0. The cache key now uses the full hash of the JWT token.