CVE-2026-40938: CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') in tektoncd pipeline
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.
AI Analysis
Technical Summary
Tekton Pipelines versions starting from 1.0.0 up to but not including 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 contain a vulnerability (CWE-88) where the git resolver's revision parameter is passed directly as a positional argument to git fetch without validation against leading '-' characters. This allows injection of arbitrary git fetch flags, such as --upload-pack, potentially leading to execution of arbitrary binaries on the resolver pod. The validateRepoURL function permits URLs beginning with '/', enabling attackers who can submit ResolutionRequest objects to chain these behaviors for code execution. Since the tekton-pipelines-resolvers ServiceAccount has cluster-wide permissions to get/list/watch all Secrets, exploitation results in full cluster-wide secret exfiltration. Fixed versions include 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1.
Potential Impact
Successful exploitation allows an attacker with permission to submit ResolutionRequest objects to execute arbitrary code on the resolver pod. Given the resolver pod's ServiceAccount has cluster-wide read access to all Kubernetes Secrets, this leads to full cluster-wide secret exfiltration. The vulnerability impacts confidentiality, integrity, and availability of the cluster environment.
Mitigation Recommendations
Fixed versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 address this vulnerability. It is recommended to upgrade affected Tekton Pipelines installations to one of these versions. No vendor advisory explicitly states alternative mitigations or that no action is required. Patch status is confirmed by vendor advisories linked from Red Hat. Users should apply the official fixes promptly.
CVE-2026-40938: CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') in tektoncd pipeline
Description
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.
CVSS v3.1
Score 7.5high
Affected software
pkg:github/tektoncd/pipelineRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Tekton Pipelines versions starting from 1.0.0 up to but not including 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 contain a vulnerability (CWE-88) where the git resolver's revision parameter is passed directly as a positional argument to git fetch without validation against leading '-' characters. This allows injection of arbitrary git fetch flags, such as --upload-pack, potentially leading to execution of arbitrary binaries on the resolver pod. The validateRepoURL function permits URLs beginning with '/', enabling attackers who can submit ResolutionRequest objects to chain these behaviors for code execution. Since the tekton-pipelines-resolvers ServiceAccount has cluster-wide permissions to get/list/watch all Secrets, exploitation results in full cluster-wide secret exfiltration. Fixed versions include 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1.
Potential Impact
Successful exploitation allows an attacker with permission to submit ResolutionRequest objects to execute arbitrary code on the resolver pod. Given the resolver pod's ServiceAccount has cluster-wide read access to all Kubernetes Secrets, this leads to full cluster-wide secret exfiltration. The vulnerability impacts confidentiality, integrity, and availability of the cluster environment.
Mitigation Recommendations
Fixed versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 address this vulnerability. It is recommended to upgrade affected Tekton Pipelines installations to one of these versions. No vendor advisory explicitly states alternative mitigations or that no action is required. Patch status is confirmed by vendor advisories linked from Red Hat. Users should apply the official fixes promptly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-15T20:40:15.518Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-40938","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:24359","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:17546","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:26538","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:26519","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:24484","vendor":"Red Hat"}]
Threat ID: 69e7e5b119fe3cd2cdfa01c5
Added to database: 04/21/2026, 21:01:37 UTC
Last enriched: 07/30/2026, 22:39:14 UTC
Last updated: 07/31/2026, 21:26:48 UTC
Views: 123
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.