Skip to content
BuildPiper CVE-2026-127080: Review hostPath access and update

BuildPiper CVE-2026-127080: Review hostPath access and update

November 13, 2026

OpsTree BuildPiper versions before 2.7.0 are affected by CVE-2026-127080. An authenticated, low-privilege user with application deployment/configuration permission can define unrestricted Kubernetes hostPath volumes. If the target cluster admits the resulting workload, access to the node filesystem can break container isolation and lead to node or cluster compromise. VulnCheck’s CNA record rates the issue Critical: CVSS 4.0 9.4 and CVSS 3.1 9.9.

The public researcher disclosure dates to November 12, 2026. The CVE record’s November 13 publication is later than that disclosure.

Confirm the update and exposure

The VulnCheck advisory sets 2.7.0 as the affected-range boundary. Researcher Neel Saurabh Kotnis says BuildPiper acknowledged and fixed the issue, but that statement does not name the fixed release. No public CVE-specific vendor release note or upgrade procedure was found.

Record the running BuildPiper version and ask the supplier to confirm a supported update to 2.7.0 or later for this CVE, including the procedure for your installation. Agree on backups, rollback and a maintenance window with the platform owner. The version boundary alone does not establish that every configuration or existing workload is safe.

Review which users can configure host volumes and deploy applications, including inherited group policies and resource scopes. The vendor’s access-management procedure describes these checks. Ordinary hostPath support alone does not prove a configuration is exploitable: the low-privilege user’s effective permissions and the target cluster’s admission policy both matter.

Restrict new mounts and review existing workloads

While arranging the update, limit host-mount configuration and deployment rights to trusted administrators. Where those rights cannot be separated, agree on a temporary deployment approval process with the platform owner. Preserve a controlled route for necessary deployments and emergency access.

Have the cluster owner enforce appropriate admission restrictions for tenant workloads. Kubernetes’ Baseline Pod Security Standard forbids hostPath volumes. Check policy coverage and exceptions in every affected tenant namespace before relying on it. Plan changes around legitimate infrastructure workloads that need host access.

Review existing workload mounts and saved deployment configurations for unexpected host access. Include init and sidecar containers: BuildPiper’s container documentation describes their host-mount option and warns about its security implications. Record each mount’s owner and approved purpose without exporting Secrets, tokens, environment values or full pod specifications.

Track the review offline on Linux

The helper reads a manually prepared CSV of sanitized workload aliases and flags recorded host mounts or unknown entries for review. It does not discover workloads or inspect BuildPiper, Kubernetes or admission policies.

With Python 3 installed, create a scratch directory:

workdir=$(mktemp -d) && cd "$workdir"

Stop if setup fails. Keep the remaining commands in the same shell. Save this synthetic example as hostpath_inventory.csv; use unknown whenever configuration has not been checked:

workload,hostpath
sample-api,no
sample-agent,yes
sample-job,unknown

Save as buildpiper_hostpath_review.py:

import argparse
import csv
import re

parser = argparse.ArgumentParser(allow_abbrev=False)
parser.add_argument("inventory")
args = parser.parse_args()
try:
    with open(args.inventory, encoding="utf-8", newline="") as source:
        rows = list(csv.reader(source, strict=True))
except (OSError, UnicodeError, csv.Error):
    parser.error("cannot read a UTF-8 CSV inventory")
if len(rows) < 2 or rows[0] != ["workload", "hostpath"]:
    parser.error("expected workload,hostpath header and at least one row")
actions = {
    "yes": "hostPath recorded; review approval and mount scope",
    "no": "no hostPath recorded; verify inventory coverage",
    "unknown": "hostPath status unknown; inspect configuration",
}
seen = set()
for number, row in enumerate(rows[1:], 2):
    if (len(row) != 2 or not re.fullmatch(r"[a-z0-9][a-z0-9-]{0,62}", row[0])
            or row[0] in seen or row[1] not in actions):
        parser.error(f"invalid or duplicate inventory row {number}")
    seen.add(row[0])
for workload, hostpath in rows[1:]:
    print(f"{workload}: {actions[hostpath]}")
print(f"Rows: {len(seen)}. Offline inventory only; no cluster or admission checks.")

Run:

python3 buildpiper_hostpath_review.py hostpath_inventory.csv

Observed on Debian 13 with Python 3.12.14, November 13, 2026, exit status 0:

sample-api: no hostPath recorded; verify inventory coverage
sample-agent: hostPath recorded; review approval and mount scope
sample-job: hostPath status unknown; inspect configuration
Rows: 3. Offline inventory only; no cluster or admission checks.

Missing files, malformed CSV, invalid states and duplicate aliases exit with status 2 before printing inventory results. A no row records a human observation, not proof of safety. An omitted workload is invisible to this helper.

Remove only these scratch files when finished:

rm -- buildpiper_hostpath_review.py hostpath_inventory.csv
cd /
rmdir -- "$workdir"
unset workdir

Verify the controls after updating

Confirm the running release with the supplier. Follow BuildPiper’s access-verification procedure with representative accounts to check intended allowed and denied actions. Have the cluster owner review admission-policy coverage and approved policy-test results, then check ordinary deployment health and emergency access. Do not deploy a host-mount probe to demonstrate the flaw.

Review available audit records for unexpected deployment or configuration changes. Logging coverage and retention determine what can be established. Investigate unexplained mounts through your incident-response process; an update is not evidence that existing mounts or a prior compromise have been removed.

The cited sources do not establish active exploitation. Only the offline helper was executed for this article; no BuildPiper installation, cluster or exploit was tested.

Acknowledgements

This post was created with assistance from AI.

Last updated on