Advisory

GHSA-67c9-f6v2-qv86

Also known as: CVE-2026-81516

Summary

Steeltoe.Discovery.Consul: malformed 'secure' metadata aborts service instance lookup (DoS)

Details

Summary

Steeltoe's Consul discovery client parses the secure metadata field on each registered service instance using bool.Parse, which throws on any value other than true or false. A single service instance registered with a malformed secure value (for example yes or 1) aborts construction of the entire instance list for that service, making the service undiscoverable. When GetAllInstancesAsync is used, one malformed instance in any service can abort enumeration across all services.
This is the same "one malformed field aborts the whole batch" availability class as CVE-2026-50196, but affecting the Consul discovery client.

Impact

Any principal that can register a service in the Consul catalog can trigger a service-discovery outage for all Steeltoe applications resolving that service. The outage affects all instances of the targeted service — not just the malformed one — and persists until the offending registration is removed.

Affected configuration

  • Application uses ConsulDiscoveryClient (any deployment).
  • The Consul catalog contains at least one service instance with a secure metadata value that is not true or false.
  • Mixed-platform environments where non-.NET clients register services with non-standard metadata values are more likely to encounter this condition.

Mitigations

If an immediate upgrade is not possible:

  • Audit the Consul catalog for service registrations with non-standard secure metadata values.
  • Restrict write access to the Consul service 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.Consul

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