CVE
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
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
- Exploited
- No known exploitation
- Fix
- Fixed in 2.7.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. BuildPiper versions before 2.7.0 Attacker submits unrestricted manifests through the Additional Manifest feature
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.43% · 37th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
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.
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”
cve.now Index
- 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
What to do
Check whether your setup matches what the bug needs.
BuildPiper versions before 2.7.0 Attacker submits unrestricted manifests through the Additional Manifest featureUpgrade 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"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- OpsTree Solutions BuildPiper
fixed in 2.7.0
Evidence 5
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
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