# Tekton v1.11.1

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

Security 5 (high 2) · Dependency updates 1

## Security (5)

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

- Affects: Git resolver API mode with a system-configured API token and a user-provided `serverURL`
- [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 user omitted `token` for a different `serverURL`, the resolver could send the system token to that server. Now the request is 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 argument injection fixed

- Affects: setups using either the deprecated or current 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)

A `revision` beginning with `-` was passed unchecked to `git fetch`, allowing injected Git flags and potentially remote 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] VolumeMount path restriction bypass fixed

- Affects: VolumeMount paths containing `..` in 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 this release, `/tekton/home/../results` passed validation and resolved to the restricted `/tekton/results` path at runtime. An authenticated user with Task or TaskRun creation permissions could exploit this to mount a volume over an internal Tekton path and potentially write fake task results trusted by downstream pipelines.

> - **[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 `refSource.URI`, an unanchored pattern could match a trusted substring and let unsigned resources pass verification. This bypass is addressed in v1.11.1, though the release does not specify how pattern 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] HTTP resolver large-response memory exhaustion fixed

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

A tenant with permission to create these runs could point the resolver at a server returning a very large response within the 1-minute timeout, potentially OOM-killing the resolver pod. Response bodies read by the resolver are now capped at 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.

## Dependency updates (1)

1 more, none mentioning security

- `* :bug: Bump google.golang.org/grpc from 1.79.3 to 1.80.0`

---

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