Critical
CVE-2026-127073: OpsTree BuildPiper Kubernetes Privilege Escalation
Inttelio Threat Feeds ·
CVE-2026-127073 is a critical privilege escalation flaw in OpsTree BuildPiper versions before 2.7.0. A low-privileged project user can submit an unrestricted manifest through the Additional Manifest feature, such as a ClusterRoleBinding to cluster-admin. The pipeline applies it with cluster-wide credentials, giving the user control over every workload and secret in the Kubernetes cluster.
| CVE | CVE-2026-127073 |
|---|---|
| CVSS v3.1 | 9.9 CRITICAL |
| Weakness | CWE-269 |
| Exploited in the wild | Not listed in CISA KEV |
| Published | November 13, 2026 |
Who is affected
Organizations running OpsTree BuildPiper versions before 2.7.0 are affected, according to the source data. Exposure is highest where BuildPiper deploys to Kubernetes clusters with cluster-wide credentials and where many people, contractors, or less-trusted users have project-level access. The source data does not list specific affected builds or editions. Check the VulnCheck advisory and OpsTree/BuildPiper for full details.
What attackers can do
An attacker needs a BuildPiper project user account. They do not need admin rights or any action from another user. Using the Additional Manifest feature, they can submit a Kubernetes manifest that BuildPiper does not restrict. One example is a ClusterRoleBinding that grants a service account the cluster-admin role. BuildPiper's pipeline applies the manifest with cluster-wide credentials, so the attacker gains full control of the cluster. That includes all workloads and all Kubernetes secrets, which may hold credentials for databases, cloud accounts, and other systems. The CVSS 3.1 score is 9.9 (Critical), with a changed scope and high impact to confidentiality, integrity, and availability.
Exploitation status
The source data has no CISA Known Exploited Vulnerabilities (KEV) entry, so there is no confirmed report of exploitation in the wild. The references include a third-party GitHub gist alongside the VulnCheck advisory, so technical details may be publicly available. The source data does not state whether a working public exploit exists. Because the attack is low-complexity and needs only a project user account, treat this as urgent.
What to do now
- Inventory every BuildPiper deployment and record its version and the Kubernetes clusters each one manages.
- Upgrade BuildPiper to version 2.7.0 or later. The data lists affected versions as 'before 2.7.0'; confirm the exact fixed release and upgrade steps with OpsTree and the VulnCheck advisory.
- Until you can upgrade, limit who holds BuildPiper project user access, and restrict or disable the Additional Manifest feature if your configuration allows it.
- Where feasible, scope the credentials BuildPiper uses to deploy so they are not cluster-wide (cluster-admin). This limits damage from this flaw and similar ones.
- Check each managed cluster for signs of abuse. Review all ClusterRoleBindings and RoleBindings that reference cluster-admin or other powerful roles, especially recently created ones or ones bound to unexpected service accounts. Remove any you cannot account for.
- Review BuildPiper pipeline history and Kubernetes audit logs for manifests submitted through Additional Manifest that create RBAC objects.
- If you find unauthorized bindings, treat the cluster as compromised. Rotate Kubernetes secrets and any credentials stored in them, and investigate workloads for tampering.
Frequently asked questions
Which BuildPiper versions are affected by CVE-2026-127073?
OpsTree BuildPiper versions before 2.7.0 are affected, according to the source data. Upgrade to 2.7.0 or later, and confirm the exact fixed release with OpsTree and the VulnCheck advisory.
Does an attacker need to be logged in to exploit CVE-2026-127073?
Yes. The attacker needs a BuildPiper project user account, which is low-privilege access. No admin rights or interaction from another user are required. With that account, they can use the Additional Manifest feature to grant themselves Kubernetes cluster-admin rights.
Is CVE-2026-127073 being exploited in the wild?
The source data does not show it. There is no CISA KEV entry for this CVE. A third-party write-up is referenced publicly. Given the 9.9 CVSS score and low attack complexity, patch promptly and check your clusters for unexpected cluster-admin bindings.
Sources
- https://nvd.nist.gov/vuln/detail/CVE-2026-127073
- https://gist.github.com/neelkotnis/7bc715e190e5be2c2fc5be15c4035ce7
- https://www.buildpiper.io/
- https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-privilege-escalation-via-additional-manifest
This briefing was drafted with AI from the official NVD and CISA records. Always confirm affected versions and fixes in the vendor advisory.
Not sure if you are exposed?
Our penetration testers find exploitable flaws before attackers do, and a vCISO can run your vulnerability program.
Talk to Inttelio