Steeltoe.Discovery.Eureka
Affected
- introduced
4.0.0, fixed4.3.0(ecosystem)
Fixed versions
4.3.0
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-81515
Steeltoe.Discovery.Eureka: malformed enum/bool/timestamp field aborts entire registry fetch (DoS)
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
EurekaDiscoveryClient (any deployment, including self-hosted Eureka).actionType, status, isCoordinatingDiscoveryServer, or timestamp fields.Mitigations
If an immediate upgrade is not possible:
High Basis: The source's own band: HIGH
4.0.0, fixed 4.3.0 (ecosystem)4.3.0
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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0