# Tekton v1.6.2

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

Security 5 (high 2) · Important fixes 1 · Dependency updates 1 · Other changes 5

## Security (5)

### [high] Git resolver token leakage to user-provided servers 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 TaskRun creator supplied a different `serverURL` without their own `token`, the resolver could send the system-configured Git API token to that server. Such requests are now rejected unless the user provides their 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 fixed

- Affects: Deployments using the current or deprecated Git resolver
- Additional action: No additional protection beyond the fix.
- [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)

When a user-supplied `revision` began with `-`, it could be parsed as a `git fetch` flag, enabling argument injection and potentially remote code execution on the resolver pod. The argument-injection path is fixed; the release does not specify how such revisions are handled now.

> - **[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] Tekton `VolumeMount` path restriction bypass fixed

- Affects: Tekton Tasks or TaskRuns using `v1` or `v1beta1` `VolumeMount` paths that reach restricted `/tekton/` internals beyond `/tekton/home`
- [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` could pass the prefix check and resolve to `/tekton/results` at runtime, potentially letting mounts overwrite internal paths and supply fake task results trusted by downstream pipelines; this traversal bypass no longer works.

> - **[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] `VerificationPolicy` substring-matching bypass fixed

- Affects: trusted resources verification with unanchored `VerificationPolicy` patterns
- [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)

An attacker able to influence `refSource.URI` could make an unanchored pattern match only part of the source, causing an unintended policy match and allowing unsigned resources to pass verification.

> - **[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] Unbounded HTTP resolver response reads fixed

- Affects: setups using the HTTP resolver (Inferred)
- [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)

A very large response from a fetched URL could exhaust the resolver pod’s memory and cause an OOM denial of service. Response-body reads are now limited to 1 MiB; the note does not specify how larger responses are handled.

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

## Important fixes (1)

### Corrupted resolver cache entries removed on type errors

- Affects: setups using the resolver cache (Inferred)

> * :bug: Remove corrupted resolver cache entries on type error

## Dependency updates (1)

### Go updated to 1.24.13

- [CVE-2025-61726](https://www.cve.org/CVERecord?id=CVE-2025-61726), [CVE-2025-61728](https://www.cve.org/CVERecord?id=CVE-2025-61728), [CVE-2025-61729](https://www.cve.org/CVERecord?id=CVE-2025-61729)

This update fixes three vulnerabilities in Go.

> * :bug: Bump Go to 1.24.13 to fix CVE-2025-61728, CVE-2025-61726, CVE-2025-61729

## Other changes (5)

- Registry image pinned
- Log-based cache assertion relaxed
- `TextParser` usage compatibility fix for `prometheus/common` v0.62.0
- Resolver cache race condition fixed with singleflight
- Resolver cache configstore aligned with the framework implementation

---

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