On this page (7 sections)
A critical flaw, CVE-2026-127080, affects OpsTree BuildPiper before version 2.7.0. According to the GitHub Advisory Database entry, an authenticated user with deploy permissions can define arbitrary Kubernetes hostPath volumes, because the platform applies no allow-list or policy checks to them.
If your team uses BuildPiper to deploy workloads to Kubernetes, this matters most to platform and DevOps administrators. A deploy-level account, which is normally trusted only with application releases, could become a path to the underlying worker node and, from there, the cluster.
What happened
The advisory was published on November 13, 2026. It describes an improper authorization problem in how BuildPiper handles a configuration labeled Define HostPath Volume. A user with deploy rights can set the host path to the root directory (/), which mounts the worker node's root filesystem into the container with read-write access.
That breaks the isolation containers are supposed to provide. The advisory states the result can be node and cluster compromise. The same text appears in the NVD record, which repeats the advisory rather than independently confirming it.
Why hostPath is risky
A hostPath volume maps a file or directory from the worker node into a pod. It is useful for a few system components, such as log collectors, but it is a well-known way to cross the boundary between a container and its host. Mounting the node root read-write means a process in the container can read and change node files, including credentials and configuration used by other workloads on that node.
The weakness here is not hostPath itself but the missing control. The advisory says BuildPiper performed no allow-list or policy check on the value, so the deploy role effectively inherited far more power than intended. The CVSS v4 metrics in the advisory show network attack vector, low complexity, low privileges required, no user interaction, and high impact on confidentiality, integrity and availability for both the vulnerable and subsequent systems.
Who is exposed
- Organizations running a BuildPiper version earlier than 2.7.0.
- Environments where many people or service accounts hold deploy permissions, since any one of them could abuse the setting.
- Clusters where BuildPiper deploys to shared worker nodes that also run sensitive workloads.
- Setups where a stolen or phished deploy account would otherwise be considered low risk.
Exploitation requires an authenticated account with deploy rights, so this is not described as an anonymous attack. The realistic risk is insider misuse or a compromised deploy credential.
How to check your exposure
First, find your BuildPiper version in the product's admin interface or through your vendor contact, and compare it with 2.7.0. Then look for workloads that already mount host paths. The following read-only command, run from a machine with kubectl access to your cluster, dumps all pods as JSON and prints lines containing hostPath entries. Review any match you do not recognize, especially a path of /.
kubectl get pods --all-namespaces -o json | grep -n '"hostPath"'For each hit, look up the pod's namespace and owner, then check who deployed it and when. Also review BuildPiper's own audit or deployment history, if available, for recent use of the Define HostPath Volume setting.
What to do now
- Confirm which BuildPiper version you run and plan an upgrade to 2.7.0 or later, verifying the fixed release with OpsTree.
- Run the hostPath listing above and investigate any pod that mounts / or other sensitive node paths.
- Review who holds deploy permissions in BuildPiper and remove access that is not needed.
- Rotate credentials for deploy accounts you cannot vouch for, and enable multi-factor authentication where the platform supports it.
- Add a cluster-side guard that does not depend on BuildPiper, such as an admission policy that restricts or allow-lists hostPath volumes (see the Kubernetes documentation for your version).
- If you find a pod that mounted the node root without a clear reason, treat that node as potentially compromised: isolate it, review it, and rotate secrets that were reachable from it.
Detection and monitoring
Kubernetes API server audit logs, if enabled, record pod creation requests including their volume definitions. Alert on new pods that declare hostPath volumes, particularly outside your system namespaces. Watch for unusual deployments by accounts that normally push application releases, and for new host-mounting pods appearing shortly after a deploy-account login from an unfamiliar location.
If BuildPiper's web interface is reachable from the internet, restrict it to a VPN or allow-listed addresses. For the public-facing side of your estate, Webforta Monitor can track certificate, DNS and header changes, though it does not inspect the inside of a Kubernetes cluster or this specific flaw.
What we do not know yet
- No exploitation in the wild is reported in the sources, and the CVE is not in the CISA known exploited vulnerabilities catalog.
- The GitHub entry is unreviewed and lists affected and patched versions as unknown; the fixed version of 2.7.0 comes from the description wording.
- We could not find a vendor release note in the research, so details such as upgrade steps or workarounds are unconfirmed.
For broader guidance, see our guide to small business website security and the security news archive.
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.
