# CVE-2026-47833: Path traversal in bpm-release

> A compromised container process can exploit symlink handling to chown host files, enabling root to read sensitive data like /etc/shadow.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** GHSA-xhf5-x86m-mrgw

## What is CVE-2026-47833?

CVE-2026-47833 is a medium-severity path traversal vulnerability in Cloud Foundry Foundation bpm-release, published on 18 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

setupBpmLogs follows symlink for bpm.log open and chown — container-to-host privilege escalation via /etc/shadow. A compromised process inside a bpm container can cause root to chown an arbitrary host file to vcap and append bpm JSON log lines to it. The chown alone lets the attacker take ownership of /etc/shadow and read every password hash on the host via the read-only /etc bind mount. This is a container-to-host confidentiality break affecting every bpm-managed job.

Affected versions: bpm-release, all versions prior to v1.4.30.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-47833 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47833 is a medium-severity path traversal vulnerability in Cloud Foundry Foundation bpm-release, published on 18 Jun 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-47833 in the wild and no public exploit code.

Affected product: Cloud Foundry Foundation bpm-release. 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-47833/ (Markdown: https://insights.sbomify.com/CVE-2026-47833/index.md)
```

## Sources

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

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