# Tekton v1.3.4

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

Security 6 (high 2) · Important fixes 1 · Other changes 1

## Security (6)

### [high] Git resolver system-token exposure to custom servers fixed

- Affects: Git resolver API mode with a system-level API token configured
- [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 its system-configured API token there. It now rejects using the system token with a non-system URL.

> - **[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 Git resolver
- [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)

Before this release, a `revision` beginning with `-` could be parsed as an injected `git fetch` flag, potentially enabling code execution on the resolver pod.

> - **[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: Task and TaskRun resources using the `v1` or `v1beta1` APIs
- [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)

Before the fix, a path such as `/tekton/home/../results` passed the prefix check but resolved to `/tekton/results` at runtime. This could let downstream pipelines trust fake task results.

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

When an attacker could influence the matched `refSource.URI`, an unanchored `spec.resources[].pattern` could match a substring and let unsigned resources 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] HTTP resolver response bodies capped at 1 MiB

- Affects: TaskRuns and PipelineRuns that reference 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 sufficiently large response from an attacker-controlled HTTP server returned within the 1-minute timeout could exhaust memory and OOM-kill the resolver pod. The note does not specify how responses larger than 1 MiB 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.

### Go 1.24.13 fixes ZIP, form, and certificate handling issues

- Affects: Tekton components using Go's `archive/zip`, `net/url`, or `crypto/x509` (Inferred)
- [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)

Before the update, opening a file in a maliciously constructed ZIP archive could cause denial of service; parsing a large URL-encoded form with many unique query parameters or formatting a hostname validation error for a certificate with many hosts could consume excessive resources. Tekton now uses Go 1.24.13, which the note says fixes these issues.

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

## Important fixes (1)

### Overcounting fixed in the `running_taskruns` metric

- Affects: setups using the `running_taskruns` metric

Before this release, its reported value was too high when TaskRuns had no condition.

> * :bug: Fix `running_taskruns` metric overcounting TaskRuns with no condition

## Other changes (1)

- Signal handling for native Kubernetes sidecars in `sidecarlogresults`

---

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