RATATOSK
← All releases

Tektonv1.10.2

Security 2

Get Tekton alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Security2critical1medium1

Git resolver path traversal fixed

critical
Affectssetups using the git resolver

Before v1.10.2, users able to create ResolutionRequests using the git resolver could supply a traversal path and read files from the resolver pod. The resolver now rejects pathInRepo values containing .. components and checks containment to prevent symlink-based escapes.

Show release-note lines
- **[GHSA-j5q5-j9gm-2w5c](https://github.com/tektoncd/pipeline/security/advisories/GHSA-j5q5-j9gm-2w5c)** (Critical): Path traversal in git resolver allows reading arbitrary files from the resolver pod. Fixed by validating the `pathInRepo` parameter to prevent directory traversal.
github.com/tektoncd/pipeline/releases/tag/v1.10.2

Long resolver names no longer panic the controller

medium
AffectsTaskRuns and PipelineRuns with custom resolver names of 31 characters or more in .spec.taskRef.resolver or .spec.pipelineRef.resolver

Before v1.10.2, these names could panic the controller, causing a restart loop that blocked reconciliation cluster-wide. The controller now truncates the resolver-name prefix to fit the DNS-1123 label limit while retaining the full hash in generated ResolutionRequest names.

Show release-note lines
- **[GHSA-cv4x-93xx-wgfj](https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj)** / CVE-2026-33022 (Medium): Controller panic via long resolver name in TaskRun/PipelineRun. A user with permission to create TaskRuns or PipelineRuns could crash the controller into a restart loop by setting a resolver name of 31+ characters, causing denial of service cluster-wide. Thanks to @1seal for reporting this vulnerability.
github.com/tektoncd/pipeline/releases/tag/v1.10.2

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.