Tekton Pipelines: Controller can panic when setting long resolver names in TaskRun/PipelineRun
Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Versions 0.60.0 through 1.0.0, 1.1.0 through 1.3.2, 1.4.0 through 1.6.0, 1.7.0 through 1.9.0, 1.10.0, and 1.10.1 have a denial-of-service vulnerability in that allows any user who can create a TaskRun or PipelineRun to crash the controller cluster-wide by setting .spec.taskRef.resolver (or .spec.pipelineRef.resolver) to a string of 31+ characters. The crash occurs because GenerateDeterministicNameFromSpec produces a name exceeding the 63-character DNS-1123 label limit, and its truncation logic panics on a [-1] slice bound since the generated name contains no spaces. Once crashed, the controller enters a CrashLoopBackOff on restart (as it re-reconciles the offending resource), blocking all CI/CD reconciliation until the resource is manually deleted. Built-in resolvers (git, cluster, bundles, hub) are unaffected due to their short names, but any custom resolver name triggers the bug. The fix truncates the resolver-name prefix instead of the full string, preserving the hash suffix for determinism and uniqueness. This issue has been patched in versions 1.0.1, 1.3.3, 1.6.1, 1.9.2 and 1.10.2.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-33022
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 23:19 UTC · Revision 1
Source evidence
Tekton Pipelines: Controller can panic when setting long resolver names in TaskRun/PipelineRun
core-osv · Original sourcePublished 20 Mar 2026, 07:48 UTC
Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Versions 0.60.0 through 1.0.0, 1.1.0 through 1.3.2, 1.4.0 through 1.6.0, 1.7.0 through 1.9.0, 1.10.0, and 1.10.1 have a denial-of-service vulnerability in that allows any user who can create a TaskRun or PipelineRun to crash the controller cluster-wide by setting .spec.taskRef.resolver (or .spec.pipelineRef.resolver) to a string of 31+ characters. The crash occurs because GenerateDeterministicNameFromSpec produces a name exceeding the 63-character DNS-1123 label limit, and its truncation logic panics on a [-1] slice bound since the generated name contains no spaces. Once crashed, the controller enters a CrashLoopBackOff on restart (as it re-reconciles the offending resource), blocking all CI/CD reconciliation until the resource is manually deleted. Built-in resolvers (git, cluster, bundles, hub) are unaffected due to their short names, but any custom resolver name triggers the bug. The fix truncates the resolver-name prefix instead of the full string, preserving the hash suffix for determinism and uniqueness. This issue has been patched in versions 1.0.1, 1.3.3, 1.6.1, 1.9.2 and 1.10.2.
osv:CVE-2026-33022
Complete source record
{
"id": "f649b2a4415f5a7747a2bf524227aee632f0f04a42ed435f05dfef2d2e4f4a1f",
"url": "https://osv.dev/vulnerability/CVE-2026-33022",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Tekton Pipelines: Controller can panic when setting long resolver names in TaskRun/PipelineRun",
"summary": "Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Versions 0.60.0 through 1.0.0, 1.1.0 through 1.3.2, 1.4.0 through 1.6.0, 1.7.0 through 1.9.0, 1.10.0, and 1.10.1 have a denial-of-service vulnerability in that allows any user who can create a TaskRun or PipelineRun to crash the controller cluster-wide by setting .spec.taskRef.resolver (or .spec.pipelineRef.resolver) to a string of 31+ characters. The crash occurs because GenerateDeterministicNameFromSpec produces a name exceeding the 63-character DNS-1123 label limit, and its truncation logic panics on a [-1] slice bound since the generated name contains no spaces. Once crashed, the controller enters a CrashLoopBackOff on restart (as it re-reconciles the offending resource), blocking all CI/CD reconciliation until the resource is manually deleted. Built-in resolvers (git, cluster, bundles, hub) are unaffected due to their short names, but any custom resolver name triggers the bug. The fix truncates the resolver-name prefix instead of the full string, preserving the hash suffix for determinism and uniqueness. This issue has been patched in versions 1.0.1, 1.3.3, 1.6.1, 1.9.2 and 1.10.2.",
"evidence": "osv:CVE-2026-33022",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-33022",
"aliases": [
"CVE-2026-33022",
"GHSA-cv4x-93xx-wgfj",
"GO-2026-4730"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/tektoncd/pipeline",
"type": "GIT",
"events": [
{
"introduced": "d649ded4ca0c48759273d7278c1022edce247fe7"
},
{
"fixed": "ec7755031a183b345cf9e64bea0e0505c1b9cb78"
},
{
"introduced": "43c0bb99fa768ff711ad92445c43179b93232877"
},
{
"fixed": "10fa538f9a2b6d01c75138f1ed7ba3da0e34687c"
},
{
"introduced": "eaf7dc1dca3e314c26d14caff8207026a2dfade7"
},
{
"fixed": "3fb58318e1805be7bdaaafcb23e42ade2edbf59c"
},
{
"introduced": "478d30f0a799663216cd225cf826e0b1efdadee3"
},
{
"fixed": "3ca7bc6e6dd1d97f80b84f78370d91edaf023cbd"
},
{
"introduced": "9db88e0a3f072ade16ad0d88f1fd6a391281cf39"
},
{
"fixed": "cdb4e1e97a4f3170f9bc2cbfff83a6c8107bc3db"
},
{
"fixed": "5eead3f859b9f938e86039e4d29185092c1d4ee6"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:linuxfoundation:tekton_pipelines:*:*:*:*:*:go:*:*",
"range": [
{
"introduced": "0.60.0"
},
{
"fixed": "1.0.1"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:linuxfoundation:tekton_pipelines:*:*:*:*:*:go:*:*",
"range": [
{
"introduced": "1.1.0"
},
{
"fixed": "1.3.3"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:linuxfoundation:tekton_pipelines:*:*:*:*:*:go:*:*",
"range": [
{
"introduced": "1.4.0"
},
{
"fixed": "1.6.1"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:linuxfoundation:tekton_pipelines:*:*:*:*:*:go:*:*",
"range": [
{
"introduced": "1.7.0"
},
{
"fixed": "1.9.2"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:linuxfoundation:tekton_pipelines:*:*:*:*:*:go:*:*",
"range": [
{
"introduced": "1.10.0"
},
{
"fixed": "1.10.2"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "5eead3f859b9f938e86039e4d29185092c1d4ee6"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v1.9.1",
"v1.10.1",
"v1.10.0",
"v1.9.0",
"v1.6.0",
"v1.7.0",
"v1.5.0",
"v1.3.2",
"v1.4.0",
"v1.3.1",
"v1.3.0",
"v1.2.0",
"v1.0.0",
"v1.1.0",
"v0.70.0",
"v0.69.0",
"v0.68.0",
"v0.66.0",
"v0.65.0",
"v0.64.0",
"v0.63.0",
"v0.62.0",
"v0.61.0",
"v0.60.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-33022.json"
}
}
],
"modified": "2026-10-28T02:30:40.512841891Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33022.json",
"https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj",
"https://nvd.nist.gov/vuln/detail/CVE-2026-33022",
"https://github.com/tektoncd/pipeline/commit/5eead3f859b9f938e86039e4d29185092c1d4ee6"
],
"provider_metadata": {
"cwe_ids": [
"CWE-129"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33022.json"
}
},
"related_cves": [
{
"value": "CVE-2026-33022",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 507944,
"published_at": "2026-03-20T07:48:15.383+00:00"
}