# CVE-2026-22727: Cloud Foundry unprotected internal endpoints

> Attackers bypassing firewalls can access unprotected internal endpoints to replace droplets, enabling code execution and data theft.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-22rx-x655-8pgg

## What is CVE-2026-22727?

CVE-2026-22727 is a high-severity missing authorization vulnerability in Cloudfoundry Cloud Foundry, published on 17 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unprotected internal endpoints in Cloud Foundry Capi Release 1.226.0 and below, and CF Deployment v54.9.0 and below on all platforms allows any user who has bypassed the firewall to potentially replace droplets and therefore applications allowing them to access secure application information.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

No fix has been published for CVE-2026-22727 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22727 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22727 is a high-severity missing authorization vulnerability in Cloudfoundry Cloud Foundry, published on 17 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22727 in the wild and no public exploit code.

Affected product: Cloudfoundry Cloud Foundry. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-22727/ (Markdown: https://insights.sbomify.com/CVE-2026-22727/index.md)
```

## Sources

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

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