Skip to main content
VulnerabilityPublished

CVE-2026-50202: SteeltoeOSS Steeltoe.Security.Authentication.CloudFoundryBase · Resource Exposure

Affects SteeltoeOSS Steeltoe.Security.Authentication.CloudFoundryBaseSource CVE Database V5

0
Compare

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

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
SteeltoeOSSSteeltoe.Security.Authentication.CloudFoundryBaseAffected
  • <3.4.0
Fixed in
  • 3.4.0
SteeltoeOSSSteeltoe.Security.Authentication.JwtBearerAffected
  • <4.2.0
Fixed in
  • 4.2.0
SteeltoeOSSSteeltoe.Security.Authentication.OpenIdConnectAffected
  • <4.2.0
Fixed in
  • 4.2.0
NuGetSteeltoeOSS/steeltoe.security.authentication.cloudfoundrybasepkg:nuget/SteeltoeOSS/steeltoe.security.authentication.cloudfoundrybaseOther threatsAffected
  • <3.4.0
Fixed in
  • 3.4.0
NuGetSteeltoeOSS/steeltoe.security.authentication.jwtbearerpkg:nuget/SteeltoeOSS/steeltoe.security.authentication.jwtbearerOther threatsAffected
  • <4.2.0
Fixed in
  • 4.2.0
NuGetSteeltoeOSS/steeltoe.security.authentication.openidconnectpkg:nuget/SteeltoeOSS/steeltoe.security.authentication.openidconnectOther threatsAffected
  • <4.2.0
Fixed in
  • 4.2.0

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

Community reviews

Loading reviews…