Advisory

GHSA-hr73-3gpv-hh6q

Also known as: CVE-2026-81515

Summary

Steeltoe.Discovery.Eureka: malformed enum/bool/timestamp field aborts entire registry fetch (DoS)

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-09-17 20:30 UTC
Modified
2026-09-17 20:45 UTC

Affected packages and fixes

Steeltoe.Discovery.Eureka

NuGet · All systems

Affected

  • introduced 4.0.0, fixed 4.3.0 (ecosystem)

Fixed versions

4.3.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