# CVE-2026-127075: OpsTree BuildPiper before 2.7.0 Path Traversal via Additional Manifest Rendering


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

## What is CVE-2026-127075?

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

### Official description

OpsTree BuildPiper before 2.7.0 contains a path traversal vulnerability that allows authenticated users to read arbitrary files by supplying traversal sequences in Additional Manifest file paths. Attackers can enter paths like ../../../../etc/passwd so the renderer embeds file contents in generated manifests and logs, exposing configuration files and service-account tokens.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-127075 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-127075 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-127075 is a high-severity vulnerability in OpsTree Solutions BuildPiper, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-127075 exists.

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

## Sources

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

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