← Back
CVE-2026-50200
high
CVSS 7.5
Information Disclosure in Steeltoe.Management.Endpoint (CVE-2026-50200)
Summary
vulnerability in Steeltoe.Management.Endpoint (CVE-2026-50200). Confidential information can be exposed externally. Exploitable via ``Sanitizer``. Mitigation: upgrade to `4.2.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-50200** has been found in Steeltoe.Management.Endpoint.
Attackers can target a specific entry point like ``Sanitizer`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade Steeltoe.Management.Endpoint to **4.2.0** or later.
If unsure, ask your IT team or search "Steeltoe.Management.Endpoint CVE-2026-50200" on the vendor's site.
CVE-2026-50200 (Steeltoe.Management.Endpoint) — CWE-200 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `Sanitizer` / `password` / `secret` / `key`
Patched: `4.2.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
**information disclosure** (CWE-200) exists in Steeltoe.Management.Endpoint. Attackers reach the vulnerable code path via ``Sanitizer`` without authentication.
📍 Affected scope
Steeltoe.Management.Endpoint — . Attack surface: `Sanitizer` / `password` / `secret` / `key`.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **4.2.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.Management.Endpoint' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Steeltoe.Management.Endpoint' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `Steeltoe.Management.Endpoint` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade Steeltoe.Management.Endpoint to 4.2.0ステージング環境で 4.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
nuget
Steeltoe.Management.Endpoint
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.0"}]}]
nuget
Steeltoe.Management.EndpointCore
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.0"}]}]
References
- web https://github.com/SteeltoeOSS/Steeltoe/commit/bef9f14b710232fca3fbe87e48fdd1b9e6b60d43
- web https://github.com/SteeltoeOSS/Steeltoe/commit/e50cd31a429b191841120f0d38fa9dda8f751b0a
- web https://github.com/SteeltoeOSS/security-advisories/security/advisories/GHSA-q62h-354g-5r85
- web https://nvd.nist.gov/vuln/detail/CVE-2026-50200
- web https://github.com/advisories/GHSA-q62h-354g-5r85