Advisory

GHSA-7fqc-p256-7pwj

Also known as: CVE-2026-50202

Summary

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

Details

Summary

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.

Impact

In multi-scheme deployments, an attacker who controls one identity provider's signing key can forge tokens accepted by other schemes within the same application. For all applications using TokenKeyResolver, a signing key removed from the identity provider's JWKS endpoint remains trusted indefinitely.

Mitigations

If an immediate upgrade is not possible:

  • In multi-scheme deployments, configure only one JwtBearer scheme per application when different identity providers are required.
  • Restart the application process after an identity provider signing key rotation to clear stale cached keys.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-07-02 20:31 UTC
Modified
2026-07-02 20:56 UTC

Affected packages and fixes

Steeltoe.Security.Authentication.JwtBearer

NuGet · All systems

Affected

  • introduced 0, fixed 4.2.0 (ecosystem)

Fixed versions

4.2.0

Fix

The export has no generic command for this ecosystem.

Steeltoe.Security.Authentication.OpenIdConnect

NuGet · All systems

Affected

  • introduced 0, fixed 4.2.0 (ecosystem)

Fixed versions

4.2.0

Fix

The export has no generic command for this ecosystem.

Steeltoe.Security.Authentication.CloudFoundryBase

NuGet · All systems

Affected

  • introduced 0, fixed 3.4.0 (ecosystem)

Fixed versions

3.4.0

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences