Skip to main content
VulnerabilityPublished

CVE-2026-127073: OpsTree Solutions BuildPiper · Improper Privilege Management

Affects OpsTree Solutions BuildPiperSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.4 Critical : upgrade to 2.7.0 as a priority.

Data as of 13 Nov 2026, 10:12 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.09.4
CNA (VulnCheck)CVSS 3.19.9
Patch
Available – fixed in 2.7.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade OpsTree Solutions BuildPiper to 2.7.0.

Affected software

ProductAffectedFixed in
OpsTree SolutionsBuildPiperAffected
  • <2.7.0
Fixed in
  • 2.7.0

AI-suggested

Upgrade BuildPiper to version 2.7.0 or later, where this privilege escalation vulnerability is fixed. No other mitigations are specified or required.

Description

OpsTree BuildPiper versions prior to 2.7.0 contain a critical privilege escalation vulnerability. This flaw allows project users to escalate their privileges to Kubernetes cluster-admin by submitting unrestricted manifests via the Additional Manifest feature. Exploitation enables attackers to deploy a ClusterRoleBinding that grants cluster-admin rights to a service account, giving control over all workloads and secrets in the cluster. The vulnerability is fixed in version 2.7.0.

References

Community reviews

Loading reviews…