# Tekton v1.0.2

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

Security 5 (high 2) · Breaking changes 1

## Security (5)

### [high] Git resolver system-token leak fixed

- Affects: Git resolver API mode with a system-configured Git API token
- [CVE-2026-40161](https://www.cve.org/CVERecord?id=CVE-2026-40161), [GHSA-wjxp-xrpv-xpff](https://github.com/tektoncd/pipeline/security/advisories/GHSA-wjxp-xrpv-xpff)

When a request omitted `token` and supplied a user-controlled `serverURL`, the resolver could send the system token there. It now rejects a non-system `serverURL` unless the request supplies its own `token`.

> - **[GHSA-wjxp-xrpv-xpff](https://github.com/tektoncd/pipeline/security/advisories/GHSA-wjxp-xrpv-xpff)** / [CVE-2026-40161](https://www.cve.org/CVERecord?id=CVE-2026-40161) (HIGH): Git resolver API mode leaks system-configured API token to user-controlled `serverURL`. A user who can create TaskRuns can exfiltrate the system Git API token by pointing the resolver at an attacker-controlled server.

### [high] Git resolver revision argument-injection vulnerability fixed

- Affects: setups using the Git resolver with user-supplied `revision` values
- [CVE-2026-40938](https://www.cve.org/CVERecord?id=CVE-2026-40938), [GHSA-94jr-7pqp-xhcq](https://github.com/tektoncd/pipeline/security/advisories/GHSA-94jr-7pqp-xhcq)

A malicious `revision` beginning with `-` could be interpreted as a `git fetch` flag, potentially allowing code execution on the resolver pod. This argument-injection vulnerability is fixed in this release.

> - **[GHSA-94jr-7pqp-xhcq](https://github.com/tektoncd/pipeline/security/advisories/GHSA-94jr-7pqp-xhcq)** / [CVE-2026-40938](https://www.cve.org/CVERecord?id=CVE-2026-40938) (HIGH): Git resolver unsanitized revision parameter enables argument injection. A malicious `revision` value can inject arbitrary flags into the `git` CLI, potentially leading to remote code execution on the resolver pod.

### [medium] `VerificationPolicy` substring-matching bypass fixed

- Affects: unanchored `VerificationPolicy` patterns in trusted-resources verification
- [CVE-2026-25542](https://www.cve.org/CVERecord?id=CVE-2026-25542), [GHSA-rmx9-2pp3-xhcr](https://github.com/tektoncd/pipeline/security/advisories/GHSA-rmx9-2pp3-xhcr)

Unanchored patterns were matched as substrings, so a source URI containing a trusted pattern could cause an unintended policy match and let unsigned resources pass verification. This affected deployments where an attacker could influence the `refSource.URI` used for matching.

> - **[GHSA-rmx9-2pp3-xhcr](https://github.com/tektoncd/pipeline/security/advisories/GHSA-rmx9-2pp3-xhcr)** / [CVE-2026-25542](https://www.cve.org/CVERecord?id=CVE-2026-25542) (Medium): VerificationPolicy regex pattern bypass via substring matching. Unanchored patterns allow partial matches, letting unsigned resources pass verification.

### [medium] Tekton VolumeMount path restriction bypass fixed

- Affects: Task and TaskRun resources using `v1` or `v1beta1` with `VolumeMount` paths under or traversing `/tekton/`
- [CVE-2026-40923](https://www.cve.org/CVERecord?id=CVE-2026-40923), [GHSA-rx35-6rhx-7858](https://github.com/tektoncd/pipeline/security/advisories/GHSA-rx35-6rhx-7858)

Paths such as `/tekton/home/../results` passed validation and resolved to `/tekton/results` because the prefix check did not normalize traversal components.

> - **[GHSA-rx35-6rhx-7858](https://github.com/tektoncd/pipeline/security/advisories/GHSA-rx35-6rhx-7858)** / [CVE-2026-40923](https://www.cve.org/CVERecord?id=CVE-2026-40923) (Medium): VolumeMount path restriction bypass via missing filepath normalization. Paths like `/tekton/../sensitive` bypass the `/tekton/` prefix restriction check.

### [medium] HTTP resolver response-body limit prevents memory exhaustion

- Affects: TaskRuns or PipelineRuns that use the HTTP resolver
- [CVE-2026-40924](https://www.cve.org/CVERecord?id=CVE-2026-40924), [GHSA-m2cx-gpqf-qf74](https://github.com/tektoncd/pipeline/security/advisories/GHSA-m2cx-gpqf-qf74)

Before this change, a very large response from a fetched URL could exhaust the resolver pod’s memory and cause an OOM, denying resolution service across the cluster. The note does not specify what happens when a response exceeds 1 MiB.

> - **[GHSA-m2cx-gpqf-qf74](https://github.com/tektoncd/pipeline/security/advisories/GHSA-m2cx-gpqf-qf74)** / [CVE-2026-40924](https://www.cve.org/CVERecord?id=CVE-2026-40924) (Medium): HTTP resolver unbounded response body read enables OOM denial of service. A malicious URL returning a very large response can exhaust the resolver pod's memory. Response body is now limited to 1 MiB.

## Breaking changes (1)

### PipelineRun `childReferences` sorting prevents spurious status updates

- Affects: PipelineRuns with `childReferences` (Inferred)

> * :bug: Sort PipelineRun `childReferences` to prevent spurious status updates

---

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