CVE-2026-127074: OpsTree BuildPiper before 2.7.0 Path Traversal via Dockerfile Path and Build Context

Published Nov 13, 2026
·
Updated

OpsTree BuildPiper before 2.7.0 contains a path traversal vulnerability that allows authenticated users with build configuration permission to read files on the build worker by supplying unvalidated dockerfilepath and build context values. Attackers can set traversal or absolute paths such as /etc/passwd via the CI configuration endpoint, then trigger a build to disclose file contents in the build log.

Affected Software

1 affected component
OpsTree BuildPiper<2.7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade OpsTree BuildPiper to a version that resolves this vulnerability.

    Fixed in 2.7.0

Event History

Nov 13, 2026
CVE Published
via MITRE·09:34 AM
Data Sourced
via MITRE·09:34 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:18 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs an authenticated account with permission to modify build configuration. They must be able to submit dockerfile_path or build context values through the CI configuration endpoint and trigger a build.

2

What systems and data are exposed?

Build workers are exposed because the supplied paths are resolved on the worker. An attacker can use traversal sequences or absolute paths, such as /etc/passwd, to read files whose contents are emitted to the build log.

3

Are default deployments affected?

The provided information does not state whether the vulnerable path handling is enabled or reachable in a default deployment. Exposure depends on whether users with build configuration permission can set the Dockerfile path or build context and run builds.

4

How can I determine whether exploitation may have occurred?

Review CI configuration changes for dockerfile_path or build context values containing traversal sequences or absolute filesystem paths. Review build logs for unexpected contents of files from the build worker.

5

What can be done if upgrading is not immediately possible?

Restrict build configuration permission to trusted users and prevent untrusted users from setting Dockerfile path or build context values. Monitor configuration changes and build logs for traversal or absolute-path inputs.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203