CVE-2026-50202

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
The EG Score, 5.9 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 17, 2026

Last Modified

June 22, 2026

Advisory Details (3)

Auto-updated Jun 17, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

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.

Affected Packages

(3 across 1 ecosystem)
NuGet(3)
PackageVulnerable rangeFix by version rangeDependents
Steeltoe.Security.Authentication.CloudFoundryBase2.2.0 ... 3.3.0 (42 versions)
  • every version up to 3.4.0: fixed in 3.4.0
—
Steeltoe.Security.Authentication.JwtBearer4.0.0, 4.0.0-beta1, 4.0.0-rc1, 4.1.0
  • every version up to 4.2.0: fixed in 4.2.0
—
Steeltoe.Security.Authentication.OpenIdConnect4.0.0, 4.0.0-beta1, 4.0.0-rc1, 4.1.0
  • every version up to 4.2.0: fixed in 4.2.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 148 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 48 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-12 15:59 UTCEG score recompute
  6. 2026-10-11 19:42 UTCEG score recompute
  7. 2026-10-11 16:57 UTCEG score recompute
  8. 2026-10-11 14:21 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-10-02 16:40 UTCOSV refresh
  20. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 38th percentile
Show 75 more
  1. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  5. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-09-13 14:07 UTCEG score recompute
  8. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-08-30 21:13 UTCEG score recompute
  18. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-08-25 04:27 UTCEG score recompute
  25. 2026-08-23 03:49 UTCEG score recompute
  26. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  27. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  28. 2026-08-21 07:24 UTCEG score recompute
  29. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  30. 2026-08-20 08:11 UTCEG score recompute
  31. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-08-19 08:05 UTCEG score recompute
  33. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  34. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  35. 2026-08-16 20:48 UTCEG score recompute
  36. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  37. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  38. 2026-08-15 18:12 UTCEG score recompute
  39. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  40. 2026-08-14 18:59 UTCEG score recompute
  41. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  42. 2026-08-12 20:33 UTCEG score recompute
  43. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  44. 2026-08-11 21:20 UTCEG score recompute
  45. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  46. 2026-08-09 22:56 UTCEG score recompute
  47. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-08-08 23:43 UTCEG score recompute
  49. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  50. 2026-08-08 00:30 UTCEG score recompute
  51. 2026-08-07 01:18 UTCEG score recompute
  52. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  53. 2026-08-06 02:06 UTCEG score recompute
  54. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  55. 2026-08-05 02:54 UTCEG score recompute
  56. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  57. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  58. 2026-08-02 04:27 UTCEG score recompute
  59. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  60. 2026-08-01 05:14 UTCEG score recompute
  61. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  62. 2026-07-31 03:54 UTCEG score recompute
  63. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  64. 2026-07-30 03:16 UTCEG score recompute
  65. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  66. 2026-07-29 01:57 UTCEG score recompute
  67. 2026-07-28 15:37 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  68. 2026-07-27 18:11 UTCEG score recompute
  69. 2026-07-26 18:58 UTCEG score recompute
  70. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  71. 2026-07-25 14:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  72. 2026-07-24 14:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  73. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  74. 2026-07-23 03:18 UTCEG score recompute
  75. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50202?
CVE-2026-50202 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-50202 published?
The CVE record for CVE-2026-50202 was published on June 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 22, 2026; the record at its source may have been updated since.
Is CVE-2026-50202 actively exploited?
CVE-2026-50202 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50202?
CVE-2026-50202 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50202?
A fix for CVE-2026-50202 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50202 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs