Steeltoe.Discovery.Eureka: malformed enum/bool/timestamp field aborts entire registry fetch (DoS)
Published 17 Sept 2026 · Updated 17 Sept 2026
Is your project on an affected Steeltoe.Discovery.Eureka?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=4.0.0 <4.3.0
- Fixed in
- 4.3.0
dotnet add package Steeltoe.Discovery.Eureka --version 4.3.0Details
Summary
Steeltoe's Eureka discovery client deserializes the registry response as a single unit. If any registered instance contains a field value that cannot be parsed (for example, an unrecognized actionType, a non-boolean value for isCoordinatingDiscoveryServer, or a non-numeric timestamp), deserialization of the entire registry fails. All Steeltoe Eureka clients connected to that registry then receive an empty or stale instance list until the malformed registration is removed.
This is a related but distinct issue from CVE-2026-50196, which addressed only the DataCenterInfo.name field.
Impact
Any principal that can register or update a service instance in the Eureka registry can trigger a service-discovery outage for all Steeltoe applications connected to the same registry. The outage persists until the offending registration is removed.
Affected configuration
- Application uses
EurekaDiscoveryClient(any deployment, including self-hosted Eureka). - The registry contains at least one service instance with an unrecognized value in a field such as
actionType,status,isCoordinatingDiscoveryServer, or timestamp fields. - Mixed-platform environments — for example, Java or Spring services co-existing in the same Eureka registry — are more likely to encounter this condition.
Mitigations
If an immediate upgrade is not possible:
- Audit the Eureka registry for registrations containing non-standard field values, particularly those originating from non-.NET clients.
- Restrict write access to the Eureka registration API to trusted services.
Is GHSA-hr73-3gpv-hh6q 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-50196Steeltoe.Discovery.Eureka: Unrecognized DataCenterInfo.Name poisons entire registry fetch · 2 Jul 2026
- LowCVE-2024-40636Steeltoe Leaks Basic Auth Credentials to Logs After Fetch Registry Error · 17 Jul 2024
References
- Linkgithub.com/SteeltoeOSS/security-advisories/security/advisories/GHSA-hr73-3gpv-hh6q
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-81515
- Linkgithub.com/SteeltoeOSS/Steeltoe/commit/bc1c3763aacc1fee82ef9932f338ec08dcb00432
- Linkgithub.com/SteeltoeOSS/Steeltoe/releases/tag/4.3.0
- Packagegithub.com/SteeltoeOSS/security-advisories
- Advisorygithub.com/advisories/GHSA-j8ph-6fxj-g533
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.