Tekton Pipelines: Git Resolver Unsanitized Revision Parameter Enables git Argument Injection Leading to RCE

Summary

Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Starting in version 1.0.0 and prior to versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1, the git resolver's revision parameter is passed directly as a positional argument to git fetch without any validation that it does not begin with a - character. Because git parses flags from mixed positional arguments, an attacker can inject arbitrary git fetch flags such as --upload-pack=<binary>. Combined with the validateRepoURL function explicitly permitting URLs that begin with / (local filesystem paths), a tenant who can submit ResolutionRequest objects can chain these two behaviors to execute an arbitrary binary on the resolver pod. The tekton-pipelines-resolvers ServiceAccount holds cluster-wide get/list/watch on all Secrets, so code execution on the resolver pod enables full cluster-wide secret exfiltration. Versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 fix the issue.

Timeline

1. Apr 21, 2026, 8:45 PM UTCCVE published
2. Apr 22, 2026, 6:31 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: total

3. Sep 7, 2026, 12:04 PM UTCRecord last updated

Affected versions

• tektoncd pipeline

  From 1.0.0 · fixed in 1.0.2; From 1.2.0 · fixed in 1.3.4; From 1.4.0 · fixed in 1.6.2; From 1.7.0 · fixed in 1.9.3; From 1.10.0 · fixed in 1.11.1

• github.com/tektoncd/pipelineGo

  From 1.0.0 · fixed in 1.0.2; From 1.1.0 · fixed in 1.3.4; From 1.4.0 · fixed in 1.6.2; From 1.7.0 · fixed in 1.9.3; From 1.10.0 · fixed in 1.11.1

• github.com/tektoncd/pipelineGo

  From 1.10.0 · fixed in 1.11.1

• github.com/tektoncd/pipelineGo

  From 1.7.0 · fixed in 1.9.3

• github.com/tektoncd/pipelineGo

  From 1.4.0 · fixed in 1.6.2

• github.com/tektoncd/pipelineGo

  From 1.2.0 · fixed in 1.3.4

• github.com/tektoncd/pipelineGo

  From 1.0.0 · fixed in 1.0.2

References 2