vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-50202

Steeltoe's static JWKS cache shared across schemes and never invalidated

MEDIUM
5.9
CVSS Score
Published: June 17, 2026 at 09:53 PM UTC
Updated: June 22, 2026 at 11:18 PM UTC
3 products affected across 1 vendorSteeltoe.Security.Authentication.JwtBearerSteeltoe.Security.Authentication.CloudFoundryBaseSteeltoe.Security.Authentication.OpenIdConnect

Using Steeltoe.Security.Authentication.CloudFoundryBase by SteeltoeOSS?

Get instant alerts when new vulnerabilities affect Steeltoe.Security.Authentication.CloudFoundryBase - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
MEDIUM5.9
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

Steeltoe is an open source project that provides a collection of libraries that helps users build cloud-native applications. In Steeltoe.Security.Authentication.CloudFoundryBase prior to version 3.4.0, Steeltoe.Security.Authentication.JwtBearer prior to version 4.2.0, and Steeltoe.Security.Authentication.OpenIdConnect prior to version 4.2.0, the JWT signing key cache in `TokenKeyResolver` uses `kid` as the sole cache key without namespacing by authority. In applications with multiple `JwtBearer` schemes pointing to different identity providers, a key fetched for one scheme can satisfy token validation for another. Additionally, cached keys have no expiration, so rotated or revoked keys remain trusted until the application process restarts. Steeltoe.Security.Authentication.CloudFoundryBase version 3.4.0, Steeltoe.Security.Authentication.JwtBearer version 4.2.0, and Steeltoe.Security.Authentication.OpenIdConnect version 4.2.0 patch the issue. If an immediate upgrade is not possible: In multi-scheme deployments, configure only one `JwtBearer` scheme per application when different identity providers are required; and/or restart the application process after an identity provider signing key rotation to clear stale cached keys.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Steeltoe.Security.Authentication.CloudFoundryBase· Steeltoeoss
60%
v < 3.4.0
Affected range stops below 3.4.0, so it looks safe — our inference, not a vendor statement
Steeltoe.Security.Authentication.JwtBearer· Steeltoeoss
60%
v < 4.2.0
Affected range stops below 4.2.0, so it looks safe — our inference, not a vendor statement
Steeltoe.Security.Authentication.OpenIdConnect· Steeltoeoss
60%
v < 4.2.0
Affected range stops below 4.2.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (3)

x_refsource_CONFIRM
Source: cverecord
https://github.com/SteeltoeOSS/security-advisories/security/advisories/GHSA-7fqc-p256-7pwj
x_refsource_MISC
Source: cverecord
https://github.com/SteeltoeOSS/Steeltoe/commit/04db2ace3b806bfe0260bb7d4bda340f241eff48
x_refsource_MISC
Source: cverecord
https://github.com/SteeltoeOSS/Steeltoe/commit/17b27b8be546ae3f83a2f6e91d45e0c84c5314b7

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.9MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-668

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card