---
id: "CVE-2026-127077"
page: "https://infrastack.ai/live/CVE-2026-127077"
kind: "vulnerability"
aliases: ["CVE-2026-127077"]
title: "OpsTree BuildPiper: authenticated users can deploy to other projects' Kubernetes clusters"
severity: "high"
cvss: 7.1
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["buildpiper", "ci-cd", "infrastructure", "kubernetes", "self-hosted"]
not_affected_if: ["dedicated-clusters-per-project", "single-project-instance"]
published_at: "2026-11-13T10:18:03+00:00"
first_seen_at: "2026-11-13T10:47:29+00:00"
updated_at: "2026-11-13T10:52:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-127077", "first_seen_at": "2026-11-13T10:47:29+00:00"}]
exploit_sources: []
---

# OpsTree BuildPiper: authenticated users can deploy to other projects' Kubernetes clusters

Link for people: https://infrastack.ai/live/CVE-2026-127077 (this .md is for agents)

OpsTree BuildPiper before 2.7.0 lets a logged-in user create environments on Kubernetes clusters that belong to another project by changing the cluster_id and namespaces values in a request. The attacker can then trigger builds and deployments into that foreign cluster, bypassing project isolation.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed BuildPiper version; versions below `2.7.0` are in scope.
- Review whether multiple projects share BuildPiper and the same Kubernetes clusters.

## Fix

- BuildPiper: upgrade to `2.7.0` or later.

## Timeline

- 2026-11-13T10:47:29+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-127077

## Documents

- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-authorization-bypass-via-environment-creation-api

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_