Most recent entries from all

Withdrawn: CLEANSTART-2026-HA54107 — Security fixes in tekton-chains 0.25.2-r1

2026-10-02T16:23:50.464171+00:00

Withdrawn by the publisher.

Affected: CleanStart: tekton-chains

Package tekton-chains version 0.25.2-r1 fixes 23 vulnerabilities: ghsa-gcjh-h69q-9w9g, ghsa-pmwq-pjrm-6p5r, CVE-2026-49478, CVE-2026-48702, CVE-2026-49834...

EUVD-2026-320115

2026-10-02T16:23:50.464216+00:00

EUVD-2026-320115

fkie_cve-2026-40923

2026-10-02T16:23:50.464232+00:00

Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Starting in version 1.0.0 and prior to versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1, a validation bypass in the VolumeMount path restriction allows mounting volumes under restricted /tekton/ internal paths by using .. path traversal components. The restriction check uses strings.HasPrefix without filepath.Clean, so a path like /tekton/home/../results passes validation but resolves to /tekton/results at runtime. Versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 fix the issue.

GHSA-rx35-6rhx-7858 — Tekton Pipelines: VolumeMount path restriction bypass via missing filepath.Clean in /tekton/ check

2026-10-02T16:23:50.464255+00:00

Affected: Go: github.com/tektoncd/pipeline

### Summary

A validation bypass in the VolumeMount path restriction allows mounting volumes under restricted `/tekton/` internal paths by using `..` path traversal components. The restriction check uses `strings.HasPrefix` without `filepath.Clean`, so a path like `/tekton/home/../results` passes validation but resolves to `/tekton/results` at runtime.

### Details

Tekton Pipelines restricts VolumeMount paths under `/tekton/` (except `/tekton/home`) to prevent users from interfering with internal execution state. The validation at `pkg/apis/pipeline/v1/container_validation.go` checks mount paths using `strings.HasPrefix` without normalizing the path first:

```go if strings.HasPrefix(vm.MountPath, "/tekton/") && !strings.HasPrefix(vm.MountPath, "/tekton/home") { // reject } ```

Because `/tekton/home` is an allowed prefix, a path like `/tekton/home/../results` passes both checks. At runtime, the container runtime resolves `..` and the actual mount point becomes `/tekton/results`.

The same pattern exists in `pkg/apis/pipeline/v1beta1/task_validation.go`.

### Impact

An authenticated user with Task or TaskRun creation permissions can mount volumes over internal Tekton paths, potentially:

- Writing fake task results that downstream pipelines trust - Reading or modifying step scripts before execution - Interfering with entrypoint coordination state

### Patches

_(to be filled: fixed in versions X.Y.Z)_

### Workarounds

- Use admission controllers (OPA/Gatekeeper, K…