CVE-2026-40161: Tekton Pipelines: Git resolver API mode leaks system-configured API token to user-controlled serverURL
Summary The Tekton Pipelines git resolver in API mode sends the system-configured Git API token to a user-controlled serverURL when the user omits the token parameter. A tenant with TaskRun or PipelineRun create permission can exfiltrate the shared API token (GitHub PAT, GitLab token, etc.) by pointing serverURL to an attacker-controlled endpoint.
Published Apr 21, 2026 · Updated May 21, 2026
Affected packages
github.com/tektoncd/pipeline
- Ecosystem
- Go
- Affected
- >= 1.0.0, < 1.0.2
- Fixed in
- 1.0.2
- Check
go list -m github.com/tektoncd/pipeline
github.com/tektoncd/pipeline
- Ecosystem
- Go
- Affected
- >= 1.2.0, < 1.3.4
- Fixed in
- 1.3.4
- Check
go list -m github.com/tektoncd/pipeline
github.com/tektoncd/pipeline
- Ecosystem
- Go
- Affected
- >= 1.4.0, < 1.6.2
- Fixed in
- 1.6.2
- Check
go list -m github.com/tektoncd/pipeline
github.com/tektoncd/pipeline
- Ecosystem
- Go
- Affected
- >= 1.7.0, < 1.9.3
- Fixed in
- 1.9.3
- Check
go list -m github.com/tektoncd/pipeline
github.com/tektoncd/pipeline
- Ecosystem
- Go
- Affected
- >= 1.10.0, < 1.11.1
- Fixed in
- 1.11.1
- Check
go list -m github.com/tektoncd/pipeline
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The Tekton Pipelines git resolver in API mode sends the system-configured Git API token to a user-controlled serverURL when the user omits the token parameter. A tenant with TaskRun or PipelineRun create permission can exfiltrate the shared API token (GitHub PAT, GitLab token, etc.) by pointing serverURL to an attacker-controlled endpoint.
Details
The git resolver's ResolveAPIGit() function in pkg/resolution/resolver/git/resolver.go constructs an SCM client using the user-supplied serverURL and a token obtained via getAPIToken().
When the user provides serverURL but omits the token parameter:
getSCMTypeAndServerURL()readsserverURLdirectly from user params (params[ServerURLParam]) with no validation against the system-configured URL.
secretRefis set tonilbecause the user did not provide a token parameter.
getAPIToken(ctx, nil, APISecretNameKey)is called. It detectsapiSecret == nil, creates a newsecretCacheKey, and populates it from the system-configured secret (conf.APISecretName/conf.APISecretNamespace/SYSTEM_NAMESPACE).
clientFunc(scmType, serverURL, string(apiToken))creates an SCM client pointed at the attacker-controlled URL with the system token. The SCM factory sets the token as anAuthorizationheader on the HTTP client.
- All subsequent API calls (
Contents.Find,Git.FindCommit) carry the system token to the attacker URL.
Impact
The system Git API token (GitHub PAT, GitLab token, etc.) is exfiltrated to an attacker-controlled endpoint. This token typically has read access to private repositories containing source code, secrets, and CI/CD configurations.
This follows the same threat model as GHSA-j5q5-j9gm-2w5c (published March 2026): a namespace-scoped tenant with permission to create TaskRuns exploits the git resolver to exfiltrate credentials. The prior advisory involved reading the resolver pod's ServiceAccount token via path traversal. This finding involves redirecting the system Git API token via serverURL.
Patches
Fixed in:
- v1.0.2 (release-v1.0.x branch)
- v1.3.4 (release-v1.3.x branch)
- v1.6.2 (release-v1.6.x branch)
- v1.9.3 (release-v1.9.x branch)
- v1.11.1 (release-v1.11.x branch)
The fix validates that when serverURL is user-provided and differs from the system-configured server URL, the user must also provide their own token parameter. Using the system token with a non-system server URL is rejected.
Workarounds
- Do not configure a system-level API token in the git resolver ConfigMap. Instead, require all users to provide their own tokens via the
tokenparameter. - Restrict TaskRun creation — limit which users or ServiceAccounts can create TaskRuns and PipelineRuns that use the git resolver.
- Network egress policies — apply
NetworkPolicyto thetekton-pipelines-resolversnamespace to restrict outbound traffic to known-good Git servers only.
Affected Versions
All releases from v1.0.0 through v1.10.0, including all patch releases. The API mode of the git resolver has been present since the resolver was introduced.
Releases prior to v1.0.0 are not affected because the git resolver either did not exist or did not have API mode.
Acknowledgments
This vulnerability was reported by Koda Reef (@kodareef5), who provided a detailed analysis and proof-of-concept. Thank you!
References
- Prior advisory: GHSA-j5q5-j9gm-2w5c
- Related: #9608 (deprecate
api-token-secret-namespace) - Related: #9609 (SubjectAccessReview for resolver secrets)
Credited to kodareef5, vdemeester, stenzopolis1986-art, waveywaves.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-25542
Tekton Pipelines has VerificationPolicy regex pattern bypass via substring matching
medium6.5Apr 21, 2026CVE-2026-40923
Tekton Pipelines: VolumeMount path restriction bypass via missing filepath.Clean in /tekton/ check
medium5.4Apr 21, 2026CVE-2026-40924
Tekton Pipelines: HTTP Resolver Unbounded Response Body Read Enables Denial of Service via Memory Exhaustion
medium6.5Apr 21, 2026CVE-2026-40938
Tekton Pipeline: Git Resolver Unsanitized Revision Parameter Enables git Argument Injection Leading to RCE
high7.5Apr 21, 2026CVE-2026-33211
Path traversal in Tekton Pipelines git resolver allows reading arbitrary files from the resolver pod
critical9.6Mar 18, 2026CVE-2026-33022
Tekton Pipelines controller panic via long resolver name in TaskRun/PipelineRun
medium6.5Mar 17, 2026
