CVE-2026-50202: SteeltoeOSS Steeltoe.Security.Authentication.CloudFoundryBase · Resource Exposure
Affects SteeltoeOSS Steeltoe.Security.Authentication.CloudFoundryBaseSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 3.4.0 when convenient.
Data as of 30 Oct 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.4.0, 4.2.0
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Steeltoe.Security.Authentication.CloudFoundryBase and SteeltoeOSS/steeltoe.security.authentication.cloudfoundrybase to 3.4.0; Steeltoe.Security.Authentication.JwtBearer and Steeltoe.Security.Authentication.OpenIdConnect and SteeltoeOSS/steeltoe.security.authentication.jwtbearer and SteeltoeOSS/steeltoe.security.authentication.openidconnect to 4.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SteeltoeOSSSteeltoe.Security.Authentication.CloudFoundryBase | Affected
| Fixed in
|
| SteeltoeOSSSteeltoe.Security.Authentication.JwtBearer | Affected
| Fixed in
|
| SteeltoeOSSSteeltoe.Security.Authentication.OpenIdConnect | Affected
| Fixed in
|
NuGetSteeltoeOSS/steeltoe.security.authentication.cloudfoundrybasepkg:nuget/SteeltoeOSS/steeltoe.security.authentication.cloudfoundrybaseOther threats | Affected
| Fixed in
|
NuGetSteeltoeOSS/steeltoe.security.authentication.jwtbearerpkg:nuget/SteeltoeOSS/steeltoe.security.authentication.jwtbearerOther threats | Affected
| Fixed in
|
NuGetSteeltoeOSS/steeltoe.security.authentication.openidconnectpkg:nuget/SteeltoeOSS/steeltoe.security.authentication.openidconnectOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in 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. Users should upgrade to these versions to resolve the issue. If immediate upgrade is not feasible, mitigate by configuring only one JwtBearer scheme per application when using different identity providers, or restart the application process after identity provider signing key rotations to clear stale cached keys.
Description
A vulnerability in Steeltoe.Security.Authentication.CloudFoundryBase and related Steeltoe authentication libraries prior to certain versions allows improper caching of JWT signing keys. The cache uses the 'kid' value without namespacing by authority, causing keys from one identity provider to be incorrectly trusted for another in multi-scheme applications. Cached keys also do not expire, so revoked or rotated keys remain trusted until the application restarts. Fixed versions address this issue by properly namespacing and managing cache expiration.
References
- github.com/SteeltoeOSS/security-advisories/security/advisories/GHSA-7fqc-p256-7pwj (opens in a new tab)
- github.com/SteeltoeOSS/Steeltoe/commit/04db2ace3b806bfe0260bb7d4bda340f241eff48 (opens in a new tab)
- github.com/SteeltoeOSS/Steeltoe/commit/17b27b8be546ae3f83a2f6e91d45e0c84c5314b7 (opens in a new tab)