# Tekton v1.9.2

2026-03-18 · [Original release notes](https://github.com/tektoncd/pipeline/releases/tag/v1.9.2) · [Full summary](https://ratatosk.io/en/releases/tekton/v1.9.2)

Security 2 (critical 1)

## Security (2)

### [critical] Git resolver path traversal fixed

- Affects: setups using the git resolver's `pathInRepo` parameter
- [CVE-2026-33211](https://www.cve.org/CVERecord?id=CVE-2026-33211), [GHSA-j5q5-j9gm-2w5c](https://github.com/tektoncd/pipeline/security/advisories/GHSA-j5q5-j9gm-2w5c)

Versions from 1.7.0 up to but excluding 1.9.2 allowed callers with permission to create `ResolutionRequests` using the git resolver to read arbitrary files from the resolver pod through path traversal, including ServiceAccount tokens. The resolver now rejects `..` path components and checks containment to block symlink-based escapes.

> - **[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.

### [medium] Long resolver names no longer crash the controller

- Affects: custom resolver names of 31 characters or more in TaskRuns or PipelineRuns
- [CVE-2026-33022](https://www.cve.org/CVERecord?id=CVE-2026-33022), [GHSA-cv4x-93xx-wgfj](https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj)

Previously, a user able to create or update a TaskRun or PipelineRun could set `.spec.taskRef.resolver` or `.spec.pipelineRef.resolver` to a name that long, crashing the controller and blocking reconciliation cluster-wide. The controller now truncates the resolver-name prefix while preserving the full hash, so long names no longer trigger the outage.

> - **[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.

---

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