Advisory

GHSA-j8ph-6fxj-g533

Also known as: CVE-2026-50196

Summary

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

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-07-02 20:30 UTC
Modified
2026-07-02 20:56 UTC

Affected packages and fixes

Steeltoe.Discovery.Eureka

NuGet · All systems

Affected

  • introduced 4.0.0, fixed 4.2.0 (ecosystem)

Fixed versions

4.2.0

Fix

The export has no generic command for this ecosystem.

Steeltoe.Discovery.Eureka

NuGet · All systems

Affected

  • introduced 0, fixed 3.4.0 (ecosystem)

Fixed versions

3.4.0

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences