Information Disclosure in Steeltoe.Management.Endpoint (CVE-2026-75523)
Summary
Vulnerability in Steeltoe.Management.Endpoint (CVE-2026-75523). Confidential information can be exposed externally. Exploitable via MaskedUri. Mitigation: upgrade to 4.3.0 or later.
Original description
The description as published by the source.
Summary
Steeltoe's /actuator/httpexchanges endpoint records and displays request URIs after passing them through MaskedUri. The masking only covers the UserInfo portion of the URI (inline user:password@host credentials) and does not inspect the query string. With IncludeQueryString enabled by default, any secrets carried in query strings (for example: OAuth tokens, password-reset tokens, signed-URL signatures, API keys) are returned verbatim in the uri field of the response and written to logs at DEBUG level.
Impact
Any caller who can reach /actuator/httpexchanges can receive full request URIs from prior traffic, including any secrets those URIs contained in their query strings. Applications with DEBUG-level logging enabled for the Steeltoe.Management.Endpoint.Actuators.HttpExchanges namespace also write these URIs to their application logs.
Affected configuration
httpexchangesis explicitly added to the actuator exposure list (Management:Endpoints:Web:Exposure:Include). It is not included by default.- The application handles requests that carry secrets in query strings, such as OAuth callbacks, signed URLs, or password-reset links.
- DEBUG logging is enabled for
Steeltoe.Management.Endpoint.Actuators.HttpExchanges(log exposure only).
Mitigations
If an immediate upgrade is not possible:
- Remove
httpexchangesfrom the actuator exposure list, or restrict it behind authentication. - Set `Management:Endpoints:HttpExchanges:IncludeQ…
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-75523 has been found in Steeltoe.Management.Endpoint.
Attackers can target a specific entry point like MaskedUri over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade Steeltoe.Management.Endpoint to 4.3.0 or later.
If unsure, ask your IT team or search "Steeltoe.Management.Endpoint CVE-2026-75523" on the vendor's site.
CVE-2026-75523 (Steeltoe.Management.Endpoint) — CWE-200 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: MaskedUri / UserInfo / IncludeQueryString / uri
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.
Information disclosure (CWE-200) exists in Steeltoe.Management.Endpoint. Attackers reach the vulnerable code path via MaskedUri without authentication.
Check the vendor advisory for the affected versions of Steeltoe.Management.Endpoint. Attack surface: MaskedUri / UserInfo / IncludeQueryString / uri.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 4.3.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Steeltoe.Management.Endpoint to 4.3.0ステージング環境で 4.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com