# Tekton v1.0.1

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

Security 2 (critical 1) · Breaking changes 1 · Important fixes 3 · Enhancements 1 · Dependency updates 1 · Other changes 12

## Security (2)

### [critical] Git resolver path traversal fixed

- Affects: installations using the git resolver where tenants can create `ResolutionRequests`
- [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 this release, tenants could use traversal in `pathInRepo` to read arbitrary files from the resolver pod, including ServiceAccount tokens, through `ResolutionRequests` or `TaskRuns` and `PipelineRuns` that use the resolver. The resolver now rejects paths with `..` components and blocks symlink escapes from attacker-controlled repositories.

> - **[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-name controller panic fixed

- Affects: TaskRuns and PipelineRuns with 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)

Before the fix, generating a deterministic `ResolutionRequest` name for one of these resources could panic the controller, causing a restart loop that blocked cluster-wide reconciliation. The controller now shortens the resolver-name prefix while retaining the full hash when generating deterministic `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.

## Breaking changes (1)

### Log results sidecar completion polling is configurable

- Affects: setups that create results using the log results sidecar

The default interval is `100ms`, reducing CPU use. A higher interval can reduce CPU load further but delay result collection, while a lower interval can provide faster feedback and may increase CPU use.

> * :hammer: The log results sidecar has been optimized to significantly reduce CPU utilization. Operators can tune the system for their environment—using a higher interval to reduce CPU load in production, or a lower interval for faster feedback in development (#8913)

## Important fixes (3)

### `tekton_pipelines_controller_running_pipelineruns` now counts only running PipelineRuns

- Affects: installations using the `tekton_pipelines_controller_running_pipelineruns` metric (Inferred)

> * :bug: fix: exclude pending PipelineRuns from `tekton_pipelines_controller_running_pipelineruns` metric (#8979) — Fixed metric to count only running PipelineRuns

### `v1beta1` Pipeline validation panic fixed

- Affects: Pipelines using the `v1beta1` API with matrix parameters

When validation encountered invalid result references in matrix parameters, it could panic. After upgrading, this validation case no longer panics.

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

### Git resolver authentication with `gitToken` fixed

- Affects: git resolver setups using `gitToken` and `gitTokenKey` for HTTP token-based authentication

When the git resolver used `gitToken` and `gitTokenKey` for HTTP token-based authentication, it failed to authenticate with those credentials. Git operations performed by the resolver now use the provided `gitToken` for remote authentication.

> * :bug: fix(#8940): Fix token-authentication header in git resolver (#8947) — Before this change, there was a regression in which the git resolver was not authenticating with the provided `gitToken` and `gitTokenKey`, breaking the git resolver's http token-based auth. After this change, all git operations performed by the git resolver use the provided `gitToken` for remote authentication.

## Enhancements (1)

- Parameter references accepted in Pipeline v1beta1 `onError`

## Dependency updates (1)

1 more, none mentioning security

- `* :hammer: build: bump Go version to 1.24.0 and fix e2e test infrastructure (#9318)`

## Other changes (12)

- Git resolver subprocess inherits pod environment
- Completed `TaskRuns` and `PipelineRuns` now allow finalizer-only updates
- GitHub Actions in CI workflows pinned to commit SHAs
- `ci-summary` job added to the `release-v1.0.x` CI workflow
- SPIRE end-to-end test image changed to `k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.0.1`
- Test images migrated from Docker Hub to `mirror.gcr.io`
- `startupProbe` added to the dind-sidecar test
- Resolver manifest changes the `TEKTON_HUB_API` default to empty
- http-resolver examples switched from Tekton Hub to ArtifactHub
- Release pipeline plumbing revision updated
- Release pipeline `precheck` task uses an updated plumbing revision
- Documentation updated to point to ArtifactHub

---

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