BuildPiper CVE-2026-127073: Restrict Additional Manifest permissions
CVE-2026-127073 affects OpsTree BuildPiper releases before 2.7.0. A project user with application deployment rights can gain Kubernetes cluster-administration privileges through Additional Manifest when the pipeline applies that user’s resources with broader, cluster-wide authority. VulnCheck rates it Critical: 9.4 in CVSS 4.0 and 9.9 in CVSS 3.1. The CNA advisory dates disclosure to November 12, 2026.
The user must be signed in and permitted to submit Additional Manifest content. Researcher Neel Saurabh Kotnis describes an escalation from application-level access to control over other workloads and cluster secrets. This is not anonymous access to arbitrary Kubernetes clusters.
Restrict the deployment path
Record the running BuildPiper version and identify applications that accept Additional Manifest input. For each, establish who can submit that content and which identity applies it to Kubernetes. Review the deployer’s effective permissions, including cluster-wide grants.
- Limit Additional Manifest editing, submission and the relevant deployment actions to trusted administrators. Use scoped policies and permission groups; review direct assignments and inherited group access. BuildPiper’s access-management procedure explains action permissions and resource scope.
- Have the platform owner give each deployment identity only the permissions its application needs. Review manifest resource-kind allowlists and approved server-side admission controls that reject unauthorized resources. The researcher’s recommendations are compensating measures, not verified descriptions of the 2.7.0 implementation.
Stage permission changes with application owners. Keep a controlled deployment route and emergency access available so that remediation does not stop necessary releases.
Triage a local inventory on Linux
This offline helper organizes a manually prepared worksheet. Its fields are not a BuildPiper export format. Use non-sensitive application aliases; enter unknown when you lack evidence. A recorded namespace restriction does not prove the pipeline enforces it.
Create a fresh directory on Linux with Python 3 installed:
workdir=$(mktemp -d) && cd "$workdir"Stop if setup fails. Keep the remaining commands in the same shell. Save this synthetic worksheet as manifest_inventory.csv:
application,additional_manifest,deployment_authority
app-a,yes,cluster-wide
app-b,yes,unknown
app-c,no,namespaceSave as buildpiper_manifest_inventory.py:
import argparse
import csv
import re
from pathlib import Path
parser = argparse.ArgumentParser(allow_abbrev=False)
parser.add_argument("inventory", type=Path)
args = parser.parse_args()
try:
with args.inventory.open(encoding="utf-8", newline="") as source:
rows = list(csv.reader(source, strict=True))
except (OSError, UnicodeError, csv.Error):
parser.error("cannot read a UTF-8 CSV inventory")
header = ["application", "additional_manifest", "deployment_authority"]
if not rows or rows[0] != header or len(rows) == 1:
parser.error("expected the documented header and at least one application")
seen = set()
for line, row in enumerate(rows[1:], 2):
if (len(row) != 3 or not re.fullmatch(r"[a-z0-9][a-z0-9-]{0,39}", row[0])
or row[1] not in {"yes", "no", "unknown"}
or row[2] not in {"cluster-wide", "namespace", "unknown"}
or row[0] in seen):
parser.error(f"invalid or duplicate application at CSV line {line}")
seen.add(row[0])
for application, manifest, authority in rows[1:]:
if "unknown" in (manifest, authority):
action = "complete the permission review"
elif manifest == "yes" and authority == "cluster-wide":
action = "prioritize the manifest/deployer boundary"
else:
action = "verify recorded restrictions and effective permissions"
print(f"{application}: {action}")
print("Inventory only; no product or cluster checks performed.")Run:
python3 buildpiper_manifest_inventory.py manifest_inventory.csvObserved on Debian 13, Python 3.12.14, November 13, 2026, exit status 0:
app-a: prioritize the manifest/deployer boundary
app-b: complete the permission review
app-c: verify recorded restrictions and effective permissions
Inventory only; no product or cluster checks performed.Invalid rows, duplicate aliases and unreadable files stop the helper with exit status 2 before it prints a review list. The script does not change the input file or connect to BuildPiper. Remove the example files when finished:
rm -- buildpiper_manifest_inventory.py manifest_inventory.csv
cd /
rmdir -- "$workdir"
unset workdirUpdate and verify
The CNA record identifies versions before 2.7.0 as affected. The researcher says BuildPiper acknowledged and fixed the issue, but that statement does not identify a release. A public vendor CVE-specific release note or upgrade procedure was not found. Arrange a supplier-supported update to 2.7.0 or a later compatible supported release, and obtain confirmation that it includes this fix. Use the supplier’s backup, recovery and upgrade instructions for your installation.
After updating, record the running version and review deployment permissions again. With representative accounts in a controlled test environment, confirm that intended application deployments still work and that restricted users cannot edit or submit Additional Manifest content. Have the platform owner verify effective deployment-identity permissions and admission-policy enforcement without creating privileged bindings. A version number alone does not establish that every configuration is safe.
Review retained deployment and Kubernetes audit metadata for unexpected permission changes. BuildPiper’s audit documentation describes configurable logging and retention; gaps in those records limit what a review can establish. Avoid exporting secrets or full request bodies. An update does not undo unauthorized changes that may already exist.
Testing covered only the offline inventory helper. No BuildPiper installation, Kubernetes cluster, product fix or exploit was tested, and the cited sources do not establish active exploitation.
Acknowledgements
This post was created with assistance from AI.