dbcve.org
Tekton PipelinesApplication · Linuxfoundation

CVE-2026-40923

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to 1.11.1 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The validation for VolumeMount paths in Tekton Pipelines uses strings.HasPrefix to restrict paths to /tekton/ directories but fails to normalize the path with filepath.Clean first. This allows path traversal via sequences like /tekton/home/../results, which passes validation but resolves to /tekton/results at runtime, enabling access to restricted internal paths.

MitigationUpgrade to Tekton Pipelines versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, or 1.11.1 which apply filepath.Clean to normalize paths before the HasPrefix validation check.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tekton PipelinesApplication
Affected:< 1.11.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Tekton Pipelines version
    Run `kubectl get tektonconfig config -o jsonpath='{.spec.pipeline.version}'` or check the installed Tekton operator version. You can also use `tkn version` if the CLI is available.
    Affected if The installed version is below 1.11.1 (or any of the patched versions: 1.0.2, 1.3.4, 1.6.2, 1.9.3)
  2. Find VolumeMount configurations in Tekton resources
    Search for Tekton TaskRun and PipelineRun resources in your cluster: `kubectl get taskrun -o yaml` and `kubectl get pipelinerun -o yaml`. Look for `volumeMounts` entries under container specs.
    Affected if Any TaskRun or PipelineRun defines VolumeMounts with custom paths (not using the default Tekton workspaces)
  3. Inspect VolumeMount paths for traversal patterns
    Examine the `mountPath` values in volumeMounts sections. Look for paths containing `../` sequences such as `/tekton/home/../results` or similar path traversal constructs.
    Affected if A VolumeMount path contains `../` which could bypass the prefix validation but resolve to restricted paths at runtime
  4. Verify path resolution behavior
    For any VolumeMount with a path starting with `/tekton/` but containing `../`, manually resolve the path to see what it actually points to. For example, `/tekton/home/../results` resolves to `/tekton/results`.
    Affected if The resolved path points to a directory outside the intended /tekton subdirectory (e.g., /tekton/results, /tekton/home when the mount was intended to be isolated to /tekton/home)

You are affected if Tekton Pipelines version is below 1.11.1 AND your Tekton resources contain VolumeMounts with paths that include `../` sequences that could resolve to restricted internal paths.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.11.1 or later
Fixed in 1.11.1
Interim mitigation

Upgrade to Tekton Pipelines versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, or 1.11.1 which apply filepath.Clean to normalize paths before the HasPrefix validation check.

Recommended fix High confidence

1.11.1

  1. Identify the current Tekton Pipelines version running in your cluster using: kubectl get tektonconfig -o jsonpath='{.items[0].spec.pipeline.version}'
  2. Check available Tekton Pipelines releases and confirm 1.11.1 is the latest stable fixed version
  3. Upgrade Tekton Pipelines to version 1.11.1 or later using your Kubernetes operator (e.g., Tekton Operator or manual kubectl apply)
  4. After upgrade, verify the installation: kubectl get tektonconfig
  5. Test that path traversal validation now properly rejects paths like /tekton/home/../results by attempting to create a VolumeMount with such paths - validation should now fail

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tekton Pipelines Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40923 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40923 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data