# CVE-2026-50201: Steeltoe's sensitive actuators (heapdump/env) only require Restricted permission

> Low-privilege users can access sensitive heap dumps and environment variables due to insufficient permission checks in Steeltoe actuators.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** GHSA-227r-jm2g-7cp4

## What is CVE-2026-50201?

CVE-2026-50201 is a medium-severity missing authorization vulnerability in SteeltoeOSS Steeltoe.Management.Endpoint, published on 17 Jun 2026. Any signed-in user can exploit it over the network, 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, all Steeltoe actuator endpoints default to `EndpointPermissions.Restricted`, which is mappeds to Cloud Foundry's `read_basic_data` permission (granted to Space Auditors and similar low-trust roles). Sensitive actuators including heap dump, environment, and thread dump do not raise this to `EndpointPermissions.Full`, so CF's `read_sensitive_data` permission flag is not enforced for those endpoints. Spring Boot's equivalent Cloud Foundry integration gates these endpoints with `read_sensitive_data` by default. Steeltoe.Management.Endpoint 4.2.0 and Steeltoe.Management.EndpointCore 3.4.0 patch the issue. If an immediate upgrade is not possible, explicitly set `RequiredPermissions = EndpointPermissions.Full` in the options for `HeapDumpEndpointOptions`, `EnvironmentEndpointOptions`, and `ThreadDumpEndpointOptions`; and/or if heap dump, thread dump, or environment are not needed in production, register only the required actuators individually instead of using `AddAllActuators()`.

Weakness: CWE-285 (Improper Authorization), CWE-269 (Improper Privilege Management)

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

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


| 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.EndpointBase` | NuGet | All versions | 3.4.0 |
| `Steeltoe.Management.EndpointBase` | NuGet | All versions | 3.4.0 |

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

Upgrade Steeltoe.Management.Endpoint to 4.2.0 or later.

## Is CVE-2026-50201 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50201 is a medium-severity missing authorization vulnerability in SteeltoeOSS Steeltoe.Management.Endpoint, published on 17 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50201 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.EndpointBase (NuGet): affected all versions; fixed in 3.4.0
- Steeltoe.Management.EndpointBase (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-50201/ (Markdown: https://insights.sbomify.com/CVE-2026-50201/index.md)
```

## Sources

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

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