Cve-2026-33211 — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/cve-2026-33211/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 24 Mar 2026 00:16:29 +0000Tekton Pipelines Git Resolver Path Traversal Vulnerabilityhttps://feed.craftedsignal.io/briefs/2026-03-tekton-traversal/Tue, 24 Mar 2026 00:16:29 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-03-tekton-traversal/The Tekton Pipelines git resolver is vulnerable to path traversal via the `pathInRepo` parameter, allowing arbitrary file reads from the resolver pod's filesystem, including ServiceAccount tokens.The Tekton Pipelines project provides Kubernetes-style resources for declaring CI/CD pipelines. A path traversal vulnerability exists in the git resolver component, tracked as CVE-2026-33211. This vulnerability affects Tekton Pipelines versions 1.0.0 and prior to 1.0.1, 1.3.3, 1.6.1, 1.9.2, and 1.10.2. An attacker with the ability to create ResolutionRequests (e.g., through TaskRuns or PipelineRuns that utilize the git resolver) can exploit this flaw to read any file from the resolver pod’s file system. A successful exploit allows attackers to retrieve sensitive information, such as ServiceAccount tokens, which are base64-encoded and returned in resolutionrequest.status.data. The vulnerability has been patched in versions 1.0.1, 1.3.3, 1.6.1, 1.9.2, and 1.10.2. This poses a significant risk in multi-tenant environments where lateral movement and privilege escalation are possible.

Attack Chain

  1. An attacker gains the ability to create TaskRuns or PipelineRuns within a Tekton Pipelines environment.
  2. The attacker crafts a malicious ResolutionRequest that leverages the git resolver.
  3. Within the ResolutionRequest, the attacker injects a path traversal sequence into the pathInRepo parameter, such as “../../../../etc/passwd”.
  4. The git resolver attempts to resolve the resource using the provided path.
  5. Due to the path traversal vulnerability, the resolver accesses the file specified by the attacker on the resolver pod’s file system.
  6. The contents of the accessed file are read by the resolver.
  7. The resolver encodes the file content in base64.
  8. The base64-encoded content is returned in the resolutionrequest.status.data field, allowing the attacker to retrieve the content. This can include sensitive files such as ServiceAccount tokens.

Impact

Successful exploitation of CVE-2026-33211 allows attackers to read arbitrary files from the Tekton Pipelines resolver pod. This can lead to the compromise of sensitive information, including ServiceAccount tokens. If ServiceAccount tokens are compromised, attackers can potentially gain unauthorized access to Kubernetes resources, leading to privilege escalation, lateral movement within the cluster, and potential data exfiltration. The impact is especially high in multi-tenant environments.

Recommendation

  • Upgrade Tekton Pipelines to versions 1.0.1, 1.3.3, 1.6.1, 1.9.2, or 1.10.2 or later to patch CVE-2026-33211.
  • Implement strict RBAC policies to limit the ability to create TaskRuns and PipelineRuns to only authorized users and service accounts.
  • Monitor Kubernetes API audit logs for suspicious ResolutionRequest creation events (see rule: “Detect Suspicious ResolutionRequest Creation”).
  • Implement network policies to restrict network access from the resolver pod to only necessary resources.
]]>criticaladvisorytektonpath-traversalkubernetescve-2026-33211cloud