OpsTree Solutions BuildPiper up to 2.6.x CI Configuration dockerfile_path/build context path traversal

Summaryinfo

A vulnerability identified as problematic has been detected in OpsTree Solutions BuildPiper up to 2.6.x. The impacted element is an unknown function of the component CI Configuration. The manipulation of the argument dockerfile_path/build context leads to path traversal. This vulnerability is traded as CVE-2026-127074. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in OpsTree Solutions BuildPiper up to 2.6.x. It has been rated as problematic. This issue affects some unknown functionality of the component CI Configuration. The manipulation of the argument dockerfile_path/build context with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. The summary by CVE is:

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 dockerfile_path 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.

The advisory is shared at gist.github.com. The identification of this vulnerability is CVE-2026-127074 since 11/12/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

Upgrading to version 2.7.0 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• OpsTree Solutions

Name

• BuildPiper

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion