On this page (8 sections)

CVE-2026-127073 is a critical privilege escalation flaw in OpsTree BuildPiper versions before 2.7.0. According to the GitHub Advisory Database entry, a user with access to a project can obtain Kubernetes cluster-admin rights by submitting unrestricted manifests through the Additional Manifest feature.

If your team runs BuildPiper to deploy into Kubernetes clusters, and more than a handful of people can create or edit projects, this deserves attention today. The advisory was published on November 13, 2026, and only one independent publisher covers it so far, so some details are still thin.

At a glance

What happened

The advisory describes a pipeline feature that trusts project users too much. BuildPiper has an Additional Manifest feature that lets a project user submit Kubernetes manifests. In affected versions, those manifests are not restricted. A project user can therefore deploy a ClusterRoleBinding that binds a service account to the built-in cluster-admin role.

The key detail is who applies the manifest. According to the advisory text, the pipeline applies it using cluster-wide credentials. The low-privileged user never needs those credentials themselves; the pipeline uses them on the user's behalf. The result, per the advisory, is control over all workloads and secrets in the cluster.

Technical details

This is a classic confused deputy problem, filed under CWE-269 (improper privilege management). A trusted component with broad rights (the pipeline) performs actions requested by a less trusted party (a project user) without checking whether the request exceeds that user's own permissions.

The CVSS v4 metrics shown on the advisory page are worth reading closely:

  • Attack vector: network, with low attack complexity and no attack requirements.
  • Privileges required: low. The attacker needs a project-level account, not an administrator.
  • User interaction: none.
  • Impact: high for confidentiality, integrity and availability, on both the vulnerable system and subsequent systems. The subsequent-system rating plausibly reflects the Kubernetes cluster behind BuildPiper, though the advisory page does not spell this out.

This article does not describe how to build a malicious manifest. The advisory also references a public gist and a VulnCheck advisory; the research did not include their contents, so we do not rely on them here.

The GitHub entry is marked Unreviewed and lists no package, affected-version range or patched version. The only version boundary available is the wording "before 2.7.0" in the description. The NVD record repeats the same text and is not independent confirmation.

Who is affected

Any organization running a BuildPiper release older than 2.7.0 that deploys to Kubernetes clusters is in scope. The realistic risk depends on who holds project accounts:

  • Platforms where many developers, contractors or customer teams have project access face the highest risk, because every one of those accounts is a possible starting point.
  • A single compromised project account, such as one with a leaked password or token, would be enough. The attacker does not need to be a malicious insider.
  • Clusters that host production workloads and secrets for multiple applications are most exposed, since cluster-admin reaches all of them.

How to check your exposure

First, confirm which BuildPiper version you run. Check the version shown in the BuildPiper admin interface or in your deployment records, and compare it with 2.7.0. If you cannot determine it, assume you are affected.

Next, look for cluster-admin grants that should not exist. The following read-only command, run with a kubectl context that has permission to read RBAC objects, lists ClusterRoleBindings and filters for those that mention cluster-admin. Look for service accounts or subjects you do not recognize.

List ClusterRoleBindings that mention cluster-admin (read-only, run with kubectl against the…Shell
kubectl get clusterrolebindings -o wide | grep cluster-admin

To see the full detail of a suspicious binding, print it as YAML. The output shows which service account or user is bound and when the object was created, which you can compare against your deployment history.

Inspect one ClusterRoleBinding in detail (read-only; replace NAME with the binding found above)Shell
kubectl get clusterrolebinding NAME -o yaml

Also review the manifests submitted through the Additional Manifest feature in your projects. Any entry that contains RBAC objects such as a ClusterRoleBinding or ClusterRole is unusual for an application deployment and should be justified by its owner.

What to do now

The sources do not name a fixed release beyond the "before 2.7.0" wording, so confirm the exact upgrade target with the vendor at buildpiper.io before you schedule the change.

  1. Identify every BuildPiper instance and its version. Treat anything older than 2.7.0 as vulnerable.
  2. Contact OpsTree or check the vendor site to confirm the fixed release, then upgrade to 2.7.0 or later.
  3. Until you have upgraded, reduce who can create or edit projects and who can use the Additional Manifest feature. Remove accounts that no longer need access.
  4. Audit ClusterRoleBindings for unexpected cluster-admin grants and review recent Additional Manifest content for RBAC objects.
  5. If you find an unexplained cluster-admin binding, treat the cluster as potentially compromised: remove the binding, review audit logs, and rotate secrets that were readable from the cluster.
  6. Rotate BuildPiper's own cluster credentials if you suspect misuse, since the pipeline holds cluster-wide access.
  7. Rotate passwords and tokens for BuildPiper project users if any account may have been exposed.
Caution. Removing a ClusterRoleBinding or rotating pipeline credentials can break running deployments. Plan the change, keep a copy of the object definitions you remove for your investigation, and test in a non-production cluster first where possible.
Tip. As a lasting control, enforce an admission policy in the cluster (for example, one that rejects creation of ClusterRoleBindings to cluster-admin by anything other than a small set of named identities). That limits the damage even if a pipeline feature trusts its users too much.

Detection and monitoring

Kubernetes API audit logs are the best evidence source. If audit logging is enabled, search for create and update events on clusterrolebindings and clusterroles, and note which identity performed them. A binding created by the pipeline's service identity shortly after a project user's deployment is the pattern to investigate.

Going forward, alert on any new binding to cluster-admin, and review RBAC changes as part of regular access reviews. Keep BuildPiper's management interface off the public internet where you can, and put it behind a VPN or an allowlist, since the advisory rates the attack vector as network. For the web-facing side of your tooling, Webforta Monitor can watch certificates, DNS and headers for unexpected changes, though it does not inspect Kubernetes RBAC.

For broader context on protecting internet-facing admin tools, see our guide to small business website security.

What is still unknown

  • The exact fixed version and release date are not given in the sources beyond "before 2.7.0".
  • No source states that the flaw is exploited in the wild, and the research shows no CISA Known Exploited Vulnerabilities listing. Absence of reports is not proof of safety.
  • The GitHub advisory is unreviewed, and only one independent publisher covers the story so far. Details may change as the vendor or other researchers publish more.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-127073 - GitHub Advisory Databasegithub.com
  2. CVE-2026-127073: OpsTree BuildPiper before 2.7.0 contains a privilege escalation vulnerability that allows project users to gain Kubernetes cluster-admin rights by submitting…nvd.nist.gov ·
  • BuildPiper
  • Kubernetes
  • privilege escalation
  • CI/CD
  • CVE-2026-127073