Loading...
Skip to main content
GeekWala

CVE-2026-50202 — Vulnerability in...

MEDIUM

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

Published July 2, 2026Updated July 2, 2026Source: osv

Summary

### 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.

Advisory Timeline

  • First published July 2, 2026 (102 days ago).
  • Last revised July 2, 2026 — 0 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

NuGet
Update Steeltoe.Security.Authentication.CloudFoundryBase to 3.4.0 or later
dotnet add package Steeltoe.Security.Authentication.CloudFoundryBase --version 3.4.0
NuGet
Update Steeltoe.Security.Authentication.JwtBearer to 4.2.0 or later
dotnet add package Steeltoe.Security.Authentication.JwtBearer --version 4.2.0
NuGet
Update Steeltoe.Security.Authentication.OpenIdConnect to 4.2.0 or later
dotnet add package Steeltoe.Security.Authentication.OpenIdConnect --version 4.2.0

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (3)

Affects 1 ecosystem: nuget (3).

PackageEcosystemAffectedFixed In
Steeltoe.Security.Authentication.CloudFoundryBase
nuget
2.2.0, 2.2.0-rc1, 2.2.0-rc2, 2.3.0 (+38 more)3.4.0
Steeltoe.Security.Authentication.JwtBearer
nuget
4.0.0, 4.0.0-beta1, 4.0.0-rc1, 4.1.04.2.0
Steeltoe.Security.Authentication.OpenIdConnect
nuget
4.0.0, 4.0.0-beta1, 4.0.0-rc1, 4.1.04.2.0

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 5.9 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
High
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

References

Frequently Asked Questions

What is CVE-2026-50202?
Steeltoe's static JWKS cache shared across schemes and never invalidated This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 5.9/10).
How do I check if my project is affected by CVE-2026-50202?
CVE-2026-50202 affects Steeltoe.Security.Authentication.CloudFoundryBase, Steeltoe.Security.Authentication.JwtBearer and Steeltoe.Security.Authentication.OpenIdConnect. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-50202 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
5.9

Exploitation requires specific conditions or has limited impact. Remediate within weeks.

Also Known As

GHSA-7fqc-p256-7pwj

Related CVEs

  • CVE-2026-106111
    MEDIUM

    ImageSharp: EXR ZIP decoder can expose stale allocator data after a short inflate

  • CVE-2026-65829
    MEDIUM

    MPXJ: Potential Path Traversal Vulnerability in Primavera P3 PRX and SureTrak STX readers

More NuGet advisories

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies