【中危】Steeltoe.Security.Authentication.JwtBearer 安全更新（GHSA-7fqc-p256-7pwj）

安全情报快照 · 风险级别：中危 · CVSS：5.9 · CVE-2026-50202 · GHSA-7fqc-p256-7pwj

先看结论

Steeltoe.Security.Authentication.JwtBearer存在安全风险，<= 4.1.0 受影响，建议升级至 4.2.0。

影响范围

处置建议

优先将 Steeltoe.Security.Authentication.JwtBearer 升级至 4.2.0 或更高版本；升级前请结合业务依赖完成兼容性验证。

上游技术详情（原文）

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.

来源与许可

• GitHub Advisory GHSA-7fqc-p256-7pwj
• 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

本页自动同步 GitHub Advisory Database 的公开数据，并保留上游原文供核验；不宣称原创分析。数据许可：CC-BY-4.0。