# Tekton v1.9.3

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

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

## Security (6)

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

- Affects: Git resolver API mode with a user-provided `serverURL` different from the system-configured server URL
- [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 `token` was omitted, the resolver could send the system-configured token to a user-controlled 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: Git resolver setups using untrusted or user-controlled `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)

Before this release, a `revision` beginning with `-` could be parsed as a Git flag. With a local-path repository URL, an attacker able to submit a `ResolutionRequest` could execute code on the resolver pod and exfiltrate cluster-wide Secrets.

> - **[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: trusted-resources verification using 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 `refSource.URI` to contain a trusted pattern as a substring, an unanchored pattern could apply an unintended policy and let unsigned resources pass verification. This release addresses the bypass, though the note does not specify how matching changed.

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

- Affects: Tasks and TaskRuns using the `v1` or `v1beta1` APIs with `VolumeMount` paths under restricted `/tekton/` paths
- [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, paths such as `/tekton/../sensitive` could bypass the `/tekton/` prefix check and resolve under a restricted path.

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

- Affects: TaskRuns and PipelineRuns using 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, fetching a very large response could exhaust the resolver pod’s memory and cause an OOM kill, denying resolution service across the cluster. HTTP resolver response bodies are now limited to 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.

### Go 1.24.13 fixes standard-library resource-exhaustion flaws

- Affects: ZIP archive handling, URL-encoded form parsing, and `crypto/x509` hostname validation (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 fix, opening a maliciously constructed ZIP archive could cause denial of service; parsing a large URL-encoded form with many unique query parameters could consume excessive memory; and constructing a hostname-validation error string for a malicious certificate could consume excessive resources.

> * :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 that emit or collect the `running_taskruns` metric (Inferred)

When TaskRuns had no condition, the metric counted too many of them.

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

## Other changes (5)

- Registry image pinned and log-based cache assertion relaxed
- Fixed `TextParser` compatibility with `prometheus/common` v0.62.0
- Corrupted resolver cache entries removed on type errors
- Resolver cache race fixed with singleflight
- Resolver cache configstore aligned with framework implementation

---

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