Summary
Steeltoe.Management.Endpoint: HttpExchanges URI masking leaks query-string secrets
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.
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:IncludeQueryStringtofalseto strip query strings from recorded exchanges entirely.
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.
CVE-2026-75523 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.3.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-75523? CVE-2026-75523 is a medium-severity security vulnerability in Steeltoe.Management.Endpoint (nuget), affecting versions <= 4.2.0. It is fixed in 4.3.0.
- How severe is CVE-2026-75523? CVE-2026-75523 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of Steeltoe.Management.Endpoint are affected by CVE-2026-75523? Steeltoe.Management.Endpoint (nuget) versions <= 4.2.0 is affected.
- Is there a fix for CVE-2026-75523? Yes. CVE-2026-75523 is fixed in 4.3.0. Upgrade to this version or later.
- Is CVE-2026-75523 exploitable, and should I be worried? Whether CVE-2026-75523 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-75523 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-75523? Upgrade
Steeltoe.Management.Endpointto 4.3.0 or later.