Steeltoe's static JWKS cache shared across schemes and never invalidated
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-50202
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 20:05 UTC · Revision 1
Source evidence
Steeltoe's static JWKS cache shared across schemes and never invalidated
core-osv · Original sourcePublished 17 Jun 2026, 21:53 UTC
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.
osv:CVE-2026-50202
Complete source record
{
"id": "0b55015f8289ea6761b9bac4f617cf3d5b11db448e4ee3d3170a073f6f8b6a06",
"url": "https://osv.dev/vulnerability/CVE-2026-50202",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Steeltoe's static JWKS cache shared across schemes and never invalidated",
"summary": "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.",
"evidence": "osv:CVE-2026-50202",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-50202",
"aliases": [
"CVE-2026-50202",
"GHSA-7fqc-p256-7pwj"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/steeltoeoss/steeltoe",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "70f147ad094c31ed5d1181592f02b3a2c439a890"
},
{
"fixed": "2d4338d0fc3990a8df90968187d9567004d3fbe7"
},
{
"fixed": "04db2ace3b806bfe0260bb7d4bda340f241eff48"
},
{
"fixed": "17b27b8be546ae3f83a2f6e91d45e0c84c5314b7"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "3.4.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"introduced": "0"
},
{
"fixed": "4.2.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "04db2ace3b806bfe0260bb7d4bda340f241eff48"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "17b27b8be546ae3f83a2f6e91d45e0c84c5314b7"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"4.1.0",
"4.0.0",
"3.3.0",
"4.0.0-rc1",
"3.2.8",
"4.0.0-beta1",
"3.2.7",
"3.2.6",
"3.2.5",
"3.2.4",
"3.2.3",
"3.2.2",
"3.2.1",
"3.2.0",
"3.2.0-rc1",
"3.1.1",
"3.1.0",
"3.1.0-rc2",
"3.1.0-rc1",
"3.0.x_2021-Jan-12",
"3.0.2",
"3.0.1",
"3.0.0",
"3.0.0-rc1",
"3.0.0-m3",
"3.0.0-m2",
"3.0.0-m1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-50202.json"
}
}
],
"modified": "2026-10-28T02:30:23.396399460Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/50xxx/CVE-2026-50202.json",
"https://github.com/SteeltoeOSS/security-advisories/security/advisories/GHSA-7fqc-p256-7pwj",
"https://nvd.nist.gov/vuln/detail/CVE-2026-50202",
"https://github.com/SteeltoeOSS/Steeltoe/commit/04db2ace3b806bfe0260bb7d4bda340f241eff48",
"https://github.com/SteeltoeOSS/Steeltoe/commit/17b27b8be546ae3f83a2f6e91d45e0c84c5314b7"
],
"provider_metadata": {
"cwe_ids": [
"CWE-668"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/50xxx/CVE-2026-50202.json"
}
},
"related_cves": [
{
"value": "CVE-2026-50202",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 489627,
"published_at": "2026-06-17T21:53:38.208+00:00"
}