RATATOSK
← All releases

Tektonv1.0.1

Security 2Breaking changes 1Important fixes 3Enhancements 1Dependency updates 1Other changes 12

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
Affectsinstallations using the git resolver where tenants can create ResolutionRequests

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.

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.0.1

Long resolver-name controller panic fixed

medium
AffectsTaskRuns and PipelineRuns with custom resolver names of 31 characters or more

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.

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.0.1

Breaking changes1

Log results sidecar completion polling is configurable

Affectssetups 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.

Show release-note lines
* :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)
github.com/tektoncd/pipeline/releases/tag/v1.0.1

Important fixes3

  • tekton_pipelines_controller_running_pipelineruns now counts only running PipelineRuns
    Affectsinstallations 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
    github.com/tektoncd/pipeline/releases/tag/v1.0.1
  • v1beta1 Pipeline validation panic fixed
    AffectsPipelines 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)
    github.com/tektoncd/pipeline/releases/tag/v1.0.1
  • Git resolver authentication with gitToken fixed
    Affectsgit 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.
    github.com/tektoncd/pipeline/releases/tag/v1.0.1

Enhancements1

Dependency updates1

    1 more, none mentioning security
    • * :hammer: build: bump Go version to 1.24.0 and fix e2e test infrastructure (#9318)
    Other changes12

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