External risk intelligence

Tekton Pipelines Path Traversal Leading to File Disclosure.

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-33211

Tekton Pipelines is a CI/CD framework deployed within internal Kubernetes clusters. The vulnerability requires authenticated access to create TaskRuns or PipelineRuns, and the affected resolver component is part of the internal orchestration architecture, not an internet-facing service or public gateway.

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in the Tekton Pipelines software, a tool used for continuous integration and delivery within Kubernetes environments. The issue allows a user with specific permissions to potentially access sensitive files, including service account tokens, from the system running Tekton Pipelines. The main concern is confirming whether this specific technology is in use and, if so, understanding the extent of potential exposure.

  • Attackers could read sensitive files on the server.
  • Impacts systems using Tekton Pipelines for CI/CD.
  • Confirm usage and assess exposure risks.

Attack Path

How an attacker could exploit the issue

An attacker with the ability to create resolution requests can exploit a path traversal vulnerability in the Tekton Pipelines git resolver. By manipulating the `pathInRepo` parameter, an attacker can read arbitrary files from the resolver pod's filesystem, potentially including sensitive ServiceAccount tokens. These file contents are then returned to the attacker, base64-encoded, within the resolution request's status data, enabling further system compromise.

  • Requires authenticated access to create requests.
  • Path traversal via `pathInRepo` parameter.
  • Access to sensitive files, including tokens.

Live Threat

Current exploitation, exposure, and threat context

A user with permission to create `ResolutionRequests` could potentially read arbitrary files from the resolver pod's filesystem, including ServiceAccount tokens. This exposure could occur when the `git-resolver` in Tekton Pipelines is configured and when the `pathInRepo` parameter is manipulated to traverse directories. The base64-encoded file contents would then be returned in the `resolutionrequest.status.data` field.

  • ServiceAccount tokens or other filesystem contents.
  • Path traversal via the `pathInRepo` parameter.
  • Exposure of sensitive information.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners or platform teams responsible for Tekton Pipelines deployments must identify all instances of the affected software, confirm their reachability and criticality, and then prioritize remediation efforts. Coordination with infrastructure and security teams will be essential for effective risk reduction and timely updates.

  • Application owners and platform teams.
  • Confirm Tekton Pipelines' reachability and criticality.
  • Plan and coordinate targeted remediation efforts.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Tekton Pipelines?

Tekton Pipelines is an open-source framework used to build CI/CD systems natively on Kubernetes. It allows developers to define and run automated pipelines that build, test, and deploy software applications by utilizing Kubernetes-style resources.

What does CVE-2026-33211 mean?

This CVE identifies a path traversal vulnerability in the Tekton Pipelines git resolver. Path traversal is a security weakness (CWE-22) that allows an attacker to manipulate file paths to access directories and files outside of the intended scope. In this case, it lets an unauthorized user read arbitrary files from the resolver pod's filesystem.

How is this vulnerability triggered?

An attacker triggers this by creating a resolution request, such as a PipelineRun or TaskRun, and specifically manipulating the `pathInRepo` parameter. If a user does not have the permissions to create these types of resolution requests, they cannot leverage this flaw to access restricted files.

Is my environment at risk from this?

According to Halo Surface Signal, this vulnerability is considered unlikely to be exploited from the internet because Tekton Pipelines typically runs within internal Kubernetes clusters. The primary risk is from someone who already has internal access to create resolution requests, rather than a remote attacker on the public web.

What should I do to secure my deployment?

You should identify all active Tekton Pipelines instances to see if they fall within the affected version ranges. Once identified, platform teams should coordinate a move to the patched versions—1.0.1, 1.3.3, 1.6.1, 1.9.2, or 1.10.2—to eliminate the underlying file access issue.

References