HighGHSA-j8ph-6fxj-g533CVE-2026-50196

Steeltoe.Discovery.Eureka: Unrecognized DataCenterInfo.Name poisons entire registry fetch

Published 2 Jul 2026 · Updated 2 Jul 2026

Is your project on an affected Steeltoe.Discovery.Eureka?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=4.0.0 <4.2.0
Fixed in
4.2.0
Update to the fixed version for your release line, for example:dotnet add package Steeltoe.Discovery.Eureka --version 4.2.0
Affected
<3.4.0
Fixed in
3.4.0
Update to the fixed version for your release line, for example:dotnet add package Steeltoe.Discovery.Eureka --version 3.4.0

Details

Summary

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.

Impact

Any registration with an unrecognized DataCenterInfo.name permanently disables service discovery for every Steeltoe Eureka client connected to the same registry. New clients start with an empty registry and running clients stop refreshing. The outage persists until the triggering registration is removed.

Because "Netflix" is valid in the Java Eureka specification, a Java or Spring service in the same mesh can trigger this unintentionally.

Affected configuration

  • Application uses the Steeltoe Eureka client (EurekaDiscoveryClient).
  • The registry contains at least one registration with a DataCenterInfo.name value other than "MyOwn" or "Amazon".

Mitigations

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.

Is GHSA-j8ph-6fxj-g533 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Steeltoe.Discovery.Eureka, and gives you the command that fixes it.

More advisories for Steeltoe.Discovery.Eureka

  • HighCVE-2026-81515Steeltoe.Discovery.Eureka: malformed enum/bool/timestamp field aborts entire registry fetch (DoS) · 17 Sept 2026
  • LowCVE-2024-40636Steeltoe Leaks Basic Auth Credentials to Logs After Fetch Registry Error · 17 Jul 2024
Steeltoe.Discovery.Eureka security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.