Critical
CVE-2026-127080: OpsTree BuildPiper HostPath Container Escape
Inttelio Threat Feeds ·
CVE-2026-127080 is a critical improper authorization flaw in OpsTree BuildPiper versions before 2.7.0. Any authenticated user with deploy rights can define Kubernetes hostPath volumes with no allow-list or policy checks. By setting the host path to / they can mount the worker node's root filesystem read-write, which breaks container isolation and can lead to compromise of the node and the cluster.
| CVE | CVE-2026-127080 |
|---|---|
| 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 before version 2.7.0 to deploy workloads to Kubernetes clusters. The risk is highest where many people or service accounts hold deploy permissions, because any of them can abuse the Define HostPath Volume setting. The source data does not list specific affected sub-versions or deployment models beyond 'before 2.7.0'. Check the VulnCheck advisory and OpsTree for full details.
What attackers can do
An attacker who holds a low-privileged deploy account in BuildPiper, or who has stolen one, can configure a workload whose hostPath volume points to / on the worker node. The node's entire root filesystem is then mounted read-write inside the container. From there the attacker can read and change files on the node, which breaks container isolation. According to the description, this can lead to full node and cluster compromise. The CVSS 3.1 score is 9.9 (network attack, low complexity, low privileges, no user interaction, changed scope), with high impact to confidentiality, integrity and availability.
Exploitation status
There is no CISA Known Exploited Vulnerabilities (KEV) entry for this CVE in the source data, so it is not confirmed as exploited in the wild. A public write-up is referenced (a GitHub gist and a VulnCheck advisory). The method is simple: set the host path to /. Treat this as an urgent patch.
What to do now
- Inventory: identify every BuildPiper instance you run and record its version. Any version before 2.7.0 is affected.
- Upgrade BuildPiper to version 2.7.0 or later. Confirm the exact upgrade steps with OpsTree and the VulnCheck advisory (https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-container-escape-via-unrestricted-hostpath-volumes).
- Until you can upgrade, limit deploy permissions in BuildPiper to the smallest set of trusted users, and review any service accounts that hold that role.
- Add a defense-in-depth control at the cluster level. Enforce Kubernetes Pod Security Admission at the 'baseline' or 'restricted' level, or use an admission policy engine, to block or allow-list hostPath volumes. That way the cluster rejects these workloads even if BuildPiper allows them.
- Check for compromise. Review BuildPiper configurations and deployed workloads for hostPath volumes, especially any that mount / or other sensitive host paths. Investigate who created them and when.
- If you find suspicious hostPath mounts, treat the affected worker nodes as potentially compromised. Rotate secrets and credentials that were reachable from those nodes, review cluster audit logs, and consider rebuilding the nodes.
- Rotate credentials for BuildPiper deploy accounts if you suspect any account has been misused or shared.
Frequently asked questions
Which BuildPiper versions are affected by CVE-2026-127080?
OpsTree BuildPiper versions before 2.7.0 are affected, according to the CVE description. Upgrading to 2.7.0 or later addresses the issue. The source data does not list more detailed version information, so check the vendor and VulnCheck advisories.
Does an attacker need an account to exploit CVE-2026-127080?
Yes. The attacker needs an authenticated BuildPiper account with deploy permissions (CVSS privileges required: Low). No user interaction is needed. Because the scope is 'changed', a low-privileged deploy user can affect the underlying Kubernetes nodes and cluster.
Is CVE-2026-127080 being exploited in the wild?
The source data contains no CISA KEV entry, so active exploitation is not confirmed. Public technical write-ups exist and the technique is simple. Given the critical 9.9 CVSS score, patch promptly.
Sources
- https://nvd.nist.gov/vuln/detail/CVE-2026-127080
- https://gist.github.com/neelkotnis/b8c1cf47f829c28086fe78d8187eb938
- https://www.buildpiper.io/
- https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-container-escape-via-unrestricted-hostpath-volumes
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