CVE-2026-50202

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.9
EG Score
5.9(medium)
EPSS
20.8%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 22, 2026

Advisory Details (3)

Auto-updated Jun 17, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Static JWKS cache shared across schemes and never invalidated · Advisory · SteeltoeOSS/security-advisories · GitHub

https://github.com/SteeltoeOSS/security-advisories/security/advisories/GHSA-7fqc-p256-7pwj
github_commit Patch Available

commit 17b27b8be546 (SteeltoeOSS/Steeltoe)

Patch available: SteeltoeOSS/Steeltoe 3.4.0 (contains commit 17b27b8be546)

https://github.com/SteeltoeOSS/Steeltoe/commit/17b27b8be546ae3f83a2f6e91d45e0c84c5314b7
github_commit Patch Available

commit 04db2ace3b80 (SteeltoeOSS/Steeltoe)

Patch available: SteeltoeOSS/Steeltoe 4.2.0 (contains commit 04db2ace3b80)

https://github.com/SteeltoeOSS/Steeltoe/commit/04db2ace3b806bfe0260bb7d4bda340f241eff48

Vendor Advisories for CVE-2026-50202(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 11:47 UTCEG score recompute
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-05 11:32 UTCEG score recompute
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 12:19 UTCEG score recompute
  7. 2026-07-03 13:03 UTCEG score recompute
  8. 2026-07-02 13:21 UTCEG score recompute
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-07-01 14:08 UTCEG score recompute
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 14:56 UTCEG score recompute
  13. 2026-06-29 15:32 UTCEG score recompute
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-28 16:20 UTCEG score recompute
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 17:07 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 17:53 UTCEG score recompute
  23. 2026-06-25 18:41 UTCEG score recompute
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-24 19:28 UTCEG score recompute
Show 21 more
  1. 2026-06-24 14:05 UTCEPSS rescore
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-23 21:33 UTCEPSS rescore
  4. 2026-06-23 19:24 UTCEG score recompute
  5. 2026-06-22 20:11 UTCEG score recompute
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-22 14:25 UTCEPSS rescore
  8. 2026-06-21 20:56 UTCEG score recompute
  9. 2026-06-21 14:56 UTCEPSS rescore
  10. 2026-06-21 14:56 UTCEPSS rescore
  11. 2026-06-21 01:59 UTCEPSS rescore
  12. 2026-06-21 01:59 UTCEPSS rescore
  13. 2026-06-20 21:41 UTCEG score recompute
  14. 2026-06-19 22:27 UTCEG score recompute
  15. 2026-06-19 19:26 UTCEPSS rescore
  16. 2026-06-19 19:26 UTCEPSS rescore
  17. 2026-06-18 23:08 UTCEG score recompute
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-17 23:51 UTCEG score recompute
  21. 2026-06-17 23:51 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-50202?
CVE-2026-50202 is a medium vulnerability published on June 17, 2026. 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…
When was CVE-2026-50202 disclosed?
CVE-2026-50202 was first published in the National Vulnerability Database on June 17, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50202 actively exploited?
CVE-2026-50202 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50202?
CVE-2026-50202 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-50202?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50202, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50202

Explore →

Is Your Infrastructure Affected by CVE-2026-50202?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.