CVE-2026-127077 · Infrastructure
NO FIX YET · SEE WHAT TO DO
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.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that run self-hosted BuildPiper with several projects deploying to shared Kubernetes clusters are exposed, since any authenticated user can target another project's cluster. Single-project installations or setups where each project has its own clusters have less exposure. The sources do not describe further configuration conditions.
Not affected if dedicated-clusters-per-project, single-project-instance
Who cares buildpiper, ci-cd, kubernetes, self-hosted
2.7.0 are in scope.2.7.0 or later.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.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.