# CVE-2026-127077: OpsTree BuildPiper before 2.7.0 Authorization Bypass via Environment Creation API


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-xm2v-p36m-5c9q

## What is CVE-2026-127077?

CVE-2026-127077 is a high-severity vulnerability in OpsTree Solutions BuildPiper, published on 13 Nov 2026. 

### Official description

OpsTree BuildPiper before 2.7.0 contains an authorization bypass vulnerability that allows authenticated users to create environments on unassigned Kubernetes clusters by tampering with cluster_id and namespaces values. Attackers can modify requests to POST /api/v1/project/{project_id}/env/ to target another project's cluster, then trigger builds and deployments into it, bypassing project isolation.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-127077 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-127077 is a high-severity vulnerability in OpsTree Solutions BuildPiper, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-127077 in the wild and no public exploit code.

Affected product: OpsTree Solutions BuildPiper. 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-127077/ (Markdown: https://insights.sbomify.com/CVE-2026-127077/index.md)
```

## Sources

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

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