CVE-2026-40938
What it is
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, the git resolver's revision parameter is passed directly as a positional argument to git fetch without any validation that it does not begin with a - character. Because git parses flags from mixed positional arguments, an attacker can inject arbitrary git fetch flags such as --upload-pack=<binary>. Combined with the validateRepoURL function explicitly permitting URLs that begin with / (local filesystem paths), a tenant who can submit ResolutionRequest objects can chain these two behaviors to execute an arbitrary binary on the resolver pod. The tekton-pipelines-resolvers ServiceAccount holds cluster-wide get/list/watch on all Secrets, so code execution on the resolver pod enables full cluster-wide secret exfiltration. Versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 fix the issue.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.8% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.8% · EPSS, next 30 days
- Weakness
- CWE-88
- Record status
- Modified
Affected
- Linuxfoundation Tekton Pipelines < 1.11.0
Attack profile CVSS 3.1 · 7.5
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-40938.md and follow it. Check whether this project is affected by CVE-2026-40938. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/tektoncd/pipeline/releases/tag/v1.11.1
- https://github.com/tektoncd/pipeline/security/advisories/GHSA-94jr-7pqp-xhcq
- https://github.com/tektoncd/pipeline/security/advisories/GHSA-94jr-7pqp-xhcq
References
- https://github.com/tektoncd/pipeline/releases/tag/v1.11.1
- https://github.com/tektoncd/pipeline/security/advisories/GHSA-94jr-7pqp-xhcq
- https://access.redhat.com/errata/RHSA-2026:17546
- https://access.redhat.com/errata/RHSA-2026:24359
- https://access.redhat.com/errata/RHSA-2026:24484
- https://access.redhat.com/errata/RHSA-2026:26519
- https://access.redhat.com/errata/RHSA-2026:26538
- https://access.redhat.com/security/cve/CVE-2026-40938
- https://bugzilla.redhat.com/show_bug.cgi?id=2460292
- https://github.com/tektoncd/pipeline/security/advisories/GHSA-94jr-7pqp-xhcq
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-40938.json