CVE-2026-127073: OpsTree BuildPiper before 2.7.0 Privilege Escalation via Additional Manifest

Published Nov 13, 2026
·
Updated

OpsTree BuildPiper before 2.7.0 contains a privilege escalation vulnerability that allows project users to gain Kubernetes cluster-admin rights by submitting unrestricted manifests through the Additional Manifest feature. Attackers can deploy a ClusterRoleBinding binding a service account to cluster-admin, which the pipeline applies with cluster-wide credentials, granting control over all workloads and secrets.

Affected Software

1 affected component
OpsTree BuildPiper<2.7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade OpsTree BuildPiper to a version that resolves this vulnerability.

    Fixed in 2.7.0

Event History

Nov 13, 2026
CVE Published
via MITRE·09:34 AM
Data Sourced
via MITRE·09:34 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:18 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

A project user who can submit manifests through the Additional Manifest feature can exploit it. The issue does not require user interaction, but it does require authenticated low-privilege access.

2

What access can an attacker gain?

An attacker can submit a ClusterRoleBinding that binds a service account to the cluster-admin role. Because the pipeline applies manifests with cluster-wide credentials, this can grant control over all workloads and secrets in the Kubernetes cluster.

3

Are default deployments affected?

The available information identifies the Additional Manifest feature as the exploitation path, but does not state whether it is enabled by default. Deployments running a version before 2.7.0 should determine whether project users can submit unrestricted additional manifests.

4

What can be done before upgrading?

Restrict or disable project-user access to the Additional Manifest feature, or ensure submitted manifests cannot create or modify cluster-scoped RBAC resources such as ClusterRoleBindings. Review pipeline credentials and limit their cluster-wide permissions where possible.

5

How can defenders look for prior exploitation?

Review applied manifests and Kubernetes audit records for unexpected ClusterRoleBindings, particularly bindings that grant cluster-admin to service accounts associated with BuildPiper pipelines or projects. Also inspect those service accounts for recently acquired cluster-admin access.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203