CVE-2026-50196

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th 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

Also known asEUVD-2026-37806 (ENISA EUVD) · GHSA-j8ph-6fxj-g533 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: 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.Discovery.Eureka prior to versions 4.2.0 and 3.4.0, DataCenterInfo.FromJson throws ArgumentException for any name value other than "MyOwn" or "Amazon", despite the Java Eureka specification defining a third valid value: "Netflix". The exception propagates through the entire registry deserialization chain and is swallowed by the periodic cache refresh task, leaving the local service registry permanently empty or stale. Versions 4.2.0 and 3.4.0 patch the issue. If an immediate upgrade is not possible, remove any registrations using unsupported DataCenterInfo.name values from the registry. In mixed Java/Spring and Steeltoe environments, audit for the Netflix data center type before deploying Steeltoe Eureka clients.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
38th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

October 26, 2026

Advisory Details (3)

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

Unrecognized DataCenterInfo.Name poisons entire registry fetch · Advisory · SteeltoeOSS/security-advisories · GitHub

https://github.com/SteeltoeOSS/security-advisories/security/advisories/GHSA-j8ph-6fxj-g533
GitHub commit Patch Available

commit c34a7399e808 (SteeltoeOSS/Steeltoe)

Patch available: SteeltoeOSS/Steeltoe 4.2.0 (contains commit c34a7399e808)

https://github.com/SteeltoeOSS/Steeltoe/commit/c34a7399e808d0d11dd977460e81df1f2722df28
GitHub commit Patch Available

commit b8ed8557bb59 (SteeltoeOSS/Steeltoe)

Patch available: SteeltoeOSS/Steeltoe 3.4.0 (contains commit b8ed8557bb59)

https://github.com/SteeltoeOSS/Steeltoe/commit/b8ed8557bb595863e4f340051d16b26ba40a75f4

Vendor Advisories for CVE-2026-50196(1)

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

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFix by version rangeDependents
Steeltoe.Discovery.Eureka3.0.0 ... 3.3.0 (21 versions)
  • 4.0.0 up to 4.2.0: fixed in 4.2.0
  • every version up to 3.4.0: fixed in 3.4.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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 172 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 72 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-50196?
CVE-2026-50196 is a high-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.Discovery.Eureka prior to versions 4.2.0 and 3.4.0, DataCenterInfo.FromJson throws ArgumentException for any name value other than "MyOwn" or "Amazon", despite…
When was the CVE record for CVE-2026-50196 published?
The CVE record for CVE-2026-50196 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 October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-50196 actively exploited?
CVE-2026-50196 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50196?
CVE-2026-50196 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50196?
A fix for CVE-2026-50196 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50196 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-50196

Explore →

Is Your Infrastructure Affected by CVE-2026-50196?

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