Skip to main content
Menu
CVEs

OpsTree BuildPiper privilege escalation in Additional Manifest feature

Affects BuildPiper versions before 2.7.0 through the Additional Manifest feature, which lets project users gain Kubernetes cluster-admin rights. Fixed in 2.7.0.

CVE-2026-127073EUVD-2026-125109GHSA-J8X6-G54C-3WG2Published November 13, 2026, updated

9.4CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 2.7.0
Who is exposed
Specific setups only

Summary

OpsTree BuildPiper before 2.7.0 contains a privilege escalation flaw that lets a project user, reachable over the network with low-privilege login, gain cluster-admin rights on the Kubernetes cluster by submitting unrestricted manifests through the Additional Manifest feature. From there, the attacker can control all workloads and secrets in the cluster.

Written by a model

Original description

OpsTree BuildPiper before 2.7.0 contains a privilege escalation vulnerability that allows project users to gain Kubernetes cluster-admin rights by submitting unrestricted manifests through the Additional Manifest feature. Attackers can deploy a ClusterRoleBinding binding a service account to cluster-admin, which the pipeline applies with cluster-wide credentials, granting control over all workloads and secrets.

Who should check

Teams running OpsTree BuildPiper before 2.7.0 that let project users use the Additional Manifest feature to submit Kubernetes manifests

“Affecting BuildPiper >= 0, < 2.7.0”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    BuildPiper versions before 2.7.0 Attacker submits unrestricted manifests through the Additional Manifest feature
  2. Upgrade to a fixed version: 2.7.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-127073 (OpsTree BuildPiper before 2.7.0 Privilege Escalation via Additional Manifest), 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-127073 (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-privilege-escalation-via-additional-manifest)
- Attacker submits unrestricted manifests through the Additional Manifest feature (source: https://www.vulncheck.com/advisories/opstree-buildpiper-before-2.7.0-privilege-escalation-via-additional-manifest)
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-127073 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127073 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-privilege-escalation-via-additional-manifest
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-127073
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-127073"}.

Affected versions

cve.now Index

18of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.4, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 13Nov 22
  • EPSS: 0.43%
  • Posted on X by cve.now Nov 13

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkbuildpiper.io · buildpiper.io
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-127073
RecordNVD · CVE-2026-127073
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
Exploitgist.github.com · neelkotnis/7bc715e190e5be2c2fc5be15c4035ce7
Other links 1
Linkvulncheck.com · advisories/opstree-buildpiper-before-2.7.0-privilege-escalation-via-additional-manifest

Questions about CVE-2026-127073

Is CVE-2026-127073 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: cve.now feed data

What does this mean?

Unrestricted manifests submitted through BuildPiper's Additional Manifest feature can give project users Kubernetes cluster-admin rights. From there they can control all workloads and secrets in the cluster.

Source: vulncheck.com

Which versions are affected by CVE-2026-127073?

BuildPiper: before 2.7.0.

Source: cve.now feed data

Am I affected, and how do I check?

BuildPiper versions before 2.7.0 are affected, and the issue involves the Additional Manifest feature. To check a installation, look at the BuildPiper version in use and whether the Additional Manifest feature is in use.

Source: vulncheck.com

How do I fix CVE-2026-127073?

Upgrade BuildPiper to version 2.7.0 or later, which is the fixed version.

Source: vulncheck.com

No corrections so far. Something wrong on this page? Report an error.