Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-81515 high CVSS 7.5

Vulnerability in Steeltoe.Discovery.Eureka (CVE-2026-81515)

Summary

Vulnerability in Steeltoe.Discovery.Eureka (CVE-2026-81515). Risk of unauthorized operations or information disclosure. Exploitable via actionType. Mitigation: upgrade to 4.3.0 or later.

Original description

The description as published by the source.

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-standa…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-81515 has been found in Steeltoe.Discovery.Eureka.
Attackers can target a specific entry point like actionType over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade Steeltoe.Discovery.Eureka to 4.3.0 or later.
If unsure, ask your IT team or search "Steeltoe.Discovery.Eureka CVE-2026-81515" on the vendor's site.

CVE-2026-81515 (Steeltoe.Discovery.Eureka) — CWE-755 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: actionType / isCoordinatingDiscoveryServer / DataCenterInfo.name / EurekaDiscoveryClient
Patched: 4.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-755) exists in Steeltoe.Discovery.Eureka. Attackers reach the vulnerable code path via actionType without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Steeltoe.Discovery.Eureka. Attack surface: actionType / isCoordinatingDiscoveryServer / DataCenterInfo.name / EurekaDiscoveryClient.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.3.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Steeltoe.Discovery.Eureka' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'Steeltoe.Discovery.Eureka' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Steeltoe.Discovery.Eureka を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade Steeltoe.Discovery.Eureka to 4.3.0

    ステージング環境で 4.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

nuget Steeltoe.Discovery.Eureka
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.3.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details