Tekton Pipelines: Git Resolver Unsanitized Revision Parameter Enables git Argument Injection Leading to RCE
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=. 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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-40938
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 02:29 UTC · Revision 1
Source evidence
Tekton Pipelines: Git Resolver Unsanitized Revision Parameter Enables git Argument Injection Leading to RCE
core-osv · Original sourcePublished 21 Apr 2026, 20:45 UTC
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=. 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.
osv:CVE-2026-40938
Complete source record
{
"id": "92745942fdaa8913b7725c96b9fe0f71577ffa2aa816593d77d2369ddebba63a",
"url": "https://osv.dev/vulnerability/CVE-2026-40938",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "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=. 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.",
"evidence": "osv:CVE-2026-40938",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-40938",
"aliases": [
"CVE-2026-40938",
"GHSA-94jr-7pqp-xhcq",
"GO-2026-5272"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/tektoncd/pipeline",
"type": "GIT",
"events": [
{
"introduced": "d9974e2cce817a43c69789161f0824e05a7572af"
},
{
"fixed": "383d57b75e404e1f6f490ed62aba9d36a98a9ff6"
},
{
"fixed": "5a882817386c72d545a7448b0793a758c0eba6b1"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:linuxfoundation:tekton_pipelines:*:*:*:*:*:go:*:*",
"range": [
{
"introduced": "1.0.0"
},
{
"fixed": "1.11.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "5a882817386c72d545a7448b0793a758c0eba6b1"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v1.11.1"
}
]
}
}
],
"versions": [
"v1.10.0",
"v1.9.0",
"v1.6.0",
"v1.7.0",
"v1.5.0",
"v1.4.0",
"v1.3.0",
"v1.2.0",
"v1.0.0",
"v1.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-40938.json"
}
}
],
"modified": "2026-10-28T02:30:49.109119154Z",
"provider": "osv",
"references": [
"https://github.com/tektoncd/pipeline/releases/tag/v1.11.1",
"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-40938.json",
"https://access.redhat.com/errata/RHSA-2026:17546",
"https://access.redhat.com/errata/RHSA-2026:24359",
"https://access.redhat.com/errata/RHSA-2026:24484",
"https://access.redhat.com/errata/RHSA-2026:26519",
"https://access.redhat.com/errata/RHSA-2026:26538",
"https://access.redhat.com/security/cve/CVE-2026-40938",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/40xxx/CVE-2026-40938.json",
"https://github.com/tektoncd/pipeline/security/advisories/GHSA-94jr-7pqp-xhcq",
"https://nvd.nist.gov/vuln/detail/CVE-2026-40938",
"https://bugzilla.redhat.com/show_bug.cgi?id=2460292"
],
"provider_metadata": {
"cwe_ids": [
"CWE-88"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/40xxx/CVE-2026-40938.json"
}
},
"related_cves": [
{
"value": "CVE-2026-40938",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 517368,
"published_at": "2026-04-21T20:45:24.658+00:00"
}