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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-50196: 0.45% estimated exploitation activity in the next 30 days; percentile 38.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

2 Jul 2026, 20:30 UTC

Last modified by the source

2 Jul 2026, 20:30 UTC

Source last checked

26 Oct 2026, 17:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j8ph-6fxj-g533

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-50196

Advisory: Steeltoe.Discovery.Eureka: Unrecognized DataCenterInfo.Name poisons entire registry fetch
IDs: CVE-2026-50196, GHSA-j8ph-6fxj-g533
Record: https://patchnext.com/advisories/cve-2026-50196 (revision 1, source checked 26 Oct 2026, 17:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: steeltoe.discovery.eureka 4.2.0, 3.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet steeltoe.discovery.eureka: affected >= 4.0.0, <= 4.1.0; <= 3.3.0; fixed in 4.2.0, 3.4.0

## Suggested inspection (read-only)
- NuGet steeltoe.discovery.eureka: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on steeltoe.discovery.eureka.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j8ph-6fxj-g533 (GitHub-reviewed advisory GHSA-j8ph-6fxj-g533 lists affected ranges: NuGet steeltoe.discovery.eureka >=4.0.0 =0 <=3.3.0)

Commands are suggestions: review each one before running it.