# Tekton v1.6.1

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

Security 2 (critical 1) · Important fixes 2 · Enhancements 1 · Other changes 5

## Security (2)

### [critical] Git resolver `pathInRepo` traversal fixed

- Affects: Tekton Pipelines git resolver setups using `pathInRepo` on versions 1.4.0 to before 1.6.1
- [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)

Before the fix, unvalidated traversal paths could let a request read arbitrary files from the resolver pod's filesystem. After upgrading, traversal paths and symlink escapes that lead outside the repository are prevented from reading those files.

> - **[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: `TaskRun` or `PipelineRun` resources using custom resolver names of 31 characters or more
- [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 resolver name of 31 characters or more could crash the controller into a restart loop, blocking reconciliation cluster-wide. The controller now truncates the resolver-name prefix to fit the DNS-1123 label limit while preserving the full hash in generated `ResolutionRequest` names.

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

## Important fixes (2)

### `v1beta1` matrix validation panic fixed

- Affects: Pipelines using the `v1beta1` API

When a matrix parameter contained an invalid result-reference expression, validation could panic while accessing the parsed expression. Validation now skips expressions that do not look like result references before parsing them, allowing the webhook to return a proper validation error.

> * :bug: fix: panic in v1beta1 matrix validation for invalid result refs (#9257) — Resolved an issue where Pipelines with invalid result references in matrix parameters would cause a panic during validation (v1beta1 API)

### PipelineRun status child references consistently sorted

- Affects: PipelineRuns with child references

An unsorted `childRef` array could trigger massive redundant status writes, especially in PipelineRuns with more than 64 child TaskRuns, contributing to apiserver memory spikes and high write QPS. Consistent sorting mitigates the resulting load and stability problems.

> * :bug: fix(pipelinerun): fix the issue of massive invalid status updates caused by unordered arrays, which will greatly impact the resource load and stability of the apiserver (#9314)

## Enhancements (1)

- Tekton `PodTemplate` supports `hostUsers` (To use: Kubernetes `UserNamespacesSupport` feature gate)

## Other changes (5)

- Immediate requeue loops stopped for TaskRuns and PipelineRuns without timeouts
- `ci-summary` job added to the `release-v1.6.x` CI workflow
- `tektoncd/plumbing` revision updated in release pipeline
- Release-pipeline `precheck` uses an updated `tektoncd/plumbing` revision
- Test reliability updates

---

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