CVE-2026-50202

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

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

Score 5.9 from GitHub Security Advisory (severity: MODERATE) published 2026-07-02. A secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-37817 (ENISA EUVD) · GHSA-7fqc-p256-7pwj (GitHub Security Advisories)Source: ENISA EUVD

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.3%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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
21st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
nugetSteeltoe.Security.Authentication.CloudFoundryBase @ 3.4.0 (fixes <= 3.3.0)—ghsa
nugetSteeltoe.Security.Authentication.JwtBearer @ 4.2.0 (fixes <= 4.1.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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 7× in last 7d / 32× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 183 rows 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 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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.3% probability of exploitation in the next 30 days (21st 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.