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

> Attackers can read database passwords from environment endpoints because the sanitizer fails to redact connection strings.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** GHSA-q62h-354g-5r85

## What is CVE-2026-50200?

CVE-2026-50200 is a high-severity vulnerability in SteeltoeOSS Steeltoe.Management.Endpoint, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-50200?

4 open source packages ship an affected version, including Steeltoe.Management.Endpoint and Steeltoe.Management.EndpointCore.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Steeltoe.Management.Endpoint` | NuGet | All versions | 4.2.0 |
| `Steeltoe.Management.Endpoint` | NuGet | All versions | 4.2.0 |
| `Steeltoe.Management.EndpointCore` | NuGet | All versions | 3.4.0 |
| `Steeltoe.Management.EndpointCore` | NuGet | All versions | 3.4.0 |

## How do I fix CVE-2026-50200?

Upgrade Steeltoe.Management.Endpoint to 4.2.0 or later.

## Is CVE-2026-50200 being exploited?

There is no known exploitation of CVE-2026-50200 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50200 and fix it if it is affected.

What it is: CVE-2026-50200 is a high-severity vulnerability in SteeltoeOSS Steeltoe.Management.Endpoint, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50200 in the wild and no public exploit code.

Affected packages and fixed versions:
- Steeltoe.Management.Endpoint (NuGet): affected all versions; fixed in 4.2.0
- Steeltoe.Management.Endpoint (NuGet): affected all versions; fixed in 4.2.0
- Steeltoe.Management.EndpointCore (NuGet): affected all versions; fixed in 3.4.0
- Steeltoe.Management.EndpointCore (NuGet): affected all versions; fixed in 3.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50200/ (Markdown: https://insights.sbomify.com/CVE-2026-50200/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50200
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50200
- OSV: https://osv.dev/vulnerability/CVE-2026-50200

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50200/
Summaries are generated and may contain mistakes; the official description above is the record.