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 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 where the git resolver's revision parameter is passed directly as a positional argument to the git fetch command without validation against arguments starting with '-'. This allows injection of arbitrary git fetch flags. Combined with the validateRepoURL function permitting repository URLs starting with '/', an attacker with permission to submit ResolutionRequest objects can execute arbitrary binaries on the resolver pod. The resolver pod's ServiceAccount has cluster-wide permissions to get/list/watch all Secrets, enabling full secret exfiltration. Exploitation complexity is high, requiring knowledge of valid local git repository paths or default URL configurations. The vulnerability is tracked as CWE-88 (Improper Neutralization of Argument Delimiters in a Command).
Potential Impact
Successful exploitation allows an authenticated user to execute arbitrary code on the resolver pod, leading to full exfiltration of cluster-wide secrets. This compromises the confidentiality and integrity of the OpenShift environment and may enable privilege escalation or lateral movement within the Kubernetes cluster. The vulnerability affects cluster security critically due to the broad permissions of the resolver pod's ServiceAccount.
Mitigation Recommendations
According to the Red Hat advisory, no official fix or patch meeting their criteria is currently available. Users are advised to upgrade to fixed versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, or 1.11.1 where the issue is resolved. If upgrading is not immediately possible, consider restricting the ability to submit ResolutionRequest objects to trusted users only, as exploitation requires authenticated access. Monitor vendor advisories for updates on official patches or mitigations.
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
tektoncd
pipeline
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 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 where the git resolver's revision parameter is passed directly as a positional argument to the git fetch command without validation against arguments starting with '-'. This allows injection of arbitrary git fetch flags. Combined with the validateRepoURL function permitting repository URLs starting with '/', an attacker with permission to submit ResolutionRequest objects can execute arbitrary binaries on the resolver pod. The resolver pod's ServiceAccount has cluster-wide permissions to get/list/watch all Secrets, enabling full secret exfiltration. Exploitation complexity is high, requiring knowledge of valid local git repository paths or default URL configurations. The vulnerability is tracked as CWE-88 (Improper Neutralization of Argument Delimiters in a Command).
Potential Impact
Successful exploitation allows an authenticated user to execute arbitrary code on the resolver pod, leading to full exfiltration of cluster-wide secrets. This compromises the confidentiality and integrity of the OpenShift environment and may enable privilege escalation or lateral movement within the Kubernetes cluster. The vulnerability affects cluster security critically due to the broad permissions of the resolver pod's ServiceAccount.
Mitigation Recommendations
According to the Red Hat advisory, no official fix or patch meeting their criteria is currently available. Users are advised to upgrade to fixed versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, or 1.11.1 where the issue is resolved. If upgrading is not immediately possible, consider restricting the ability to submit ResolutionRequest objects to trusted users only, as exploitation requires authenticated access. Monitor vendor advisories for updates on official patches or mitigations.
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
- 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: 08/17/2026, 13:19:31 UTC
Last updated: 09/13/2026, 22:12:47 UTC
Views: 155
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.