SteeltoeOSS Steeltoe.Security.Authentication.CloudFoundryBase up to 3.3.x JWT Signing Key exposure of resource
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 1.89 |
Summary
A vulnerability marked as problematic has been reported in SteeltoeOSS Steeltoe.Security.Authentication.CloudFoundryBase, Steeltoe.Security.Authentication.JwtBearer and Steeltoe.Security.Authentication.OpenIdConnect up to 3.3.x. The impacted element is an unknown function of the component JWT Signing Key Handler. Performing a manipulation results in exposure of resource. This vulnerability is cataloged as CVE-2026-50202. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in SteeltoeOSS Steeltoe.Security.Authentication.CloudFoundryBase, Steeltoe.Security.Authentication.JwtBearer and Steeltoe.Security.Authentication.OpenIdConnect up to 3.3.x. This affects an unknown code of the component JWT Signing Key Handler. The manipulation with an unknown input leads to a exposure of resource vulnerability. CWE is classifying the issue as CWE-668. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-50202 since 06/04/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Additional levels of successful authentication are needed for exploitation. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 3.4.0 eliminates this vulnerability. Applying the patch 04db2ace3b806bfe0260bb7d4bda340f241eff48 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
- Steeltoe.Security.Authentication.CloudFoundryBase
- Steeltoe.Security.Authentication.JwtBearer
- Steeltoe.Security.Authentication.OpenIdConnect
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 4.1
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.9
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Exposure of resourceCWE: CWE-668 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Steeltoe.Security.Authentication.CloudFoundryBase/Steeltoe.Security.Authentication.JwtBearer/Steeltoe.Security.Authentication.OpenIdConnect 3.4.0
Patch: 04db2ace3b806bfe0260bb7d4bda340f241eff48
Timeline
06/04/2026 CVE reserved06/18/2026 Advisory disclosed
06/18/2026 VulDB entry created
06/18/2026 VulDB entry last update
Sources
Advisory: GHSA-7fqc-p256-7pwjStatus: Confirmed
CVE: CVE-2026-50202 (🔒)
GCVE (CVE): GCVE-0-2026-50202
GCVE (VulDB): GCVE-100-372159
Entry
Created: 06/18/2026 07:41Changes: 06/18/2026 07:41 (67)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.