{"id":"EUVD-2026-13615","revision":"fbab90aa5d7f430ebbac816c072eb62a","records":[{"revision":"fbab90aa5d7f430ebbac816c072eb62a","observedAt":"2026-11-09T08:08:05.507+00:00","statement":{"source":"euvd","id":"EUVD-2026-13615","aliases":["CVE-2026-33022","GHSA-cv4x-93xx-wgfj"],"title":"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 vulnerabili…","description":"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.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","score":6.5,"severity":null}],"references":["https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj","https://github.com/tektoncd/pipeline/commit/5eead3f859b9f938e86039e4d29185092c1d4ee6"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-13615","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Mar 20, 2026, 7:48:15 AM","dateUpdated":"Mar 20, 2026, 6:07:35 PM"},"relatedAdvisories":[{"id":"RHSA-2026:10026","title":"Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.20.4","vulnerabilityIds":["CVE-2026-33022","CVE-2026-33211"]},{"id":"RHSA-2026:10066","title":"Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.20.4","vulnerabilityIds":["CVE-2026-33022","CVE-2026-33211"]},{"id":"WID-SEC-W-2026-1249","title":"Red Hat OpenShift Pipelines: Mehrere Schwachstellen","vulnerabilityIds":["CVE-2026-33022","CVE-2026-33211"]},{"id":"RHSA-2026:6166","title":"Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.21.1","vulnerabilityIds":["CVE-2025-66506","CVE-2026-33022","CVE-2026-33211"]},{"id":"RHSA-2026:6170","title":"Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.21.1","vulnerabilityIds":["CVE-2025-66506","CVE-2026-25639","CVE-2026-33022","CVE-2026-33211"]}],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2026-13615","identifiers":["EUVD-2026-13615","CVE-2026-33022","GHSA-cv4x-93xx-wgfj"]},"retained":false,"historicalAffected":[]}],"coverage":[]}