Skip to main content
VulnerabilityPublished Updated

CVE-2026-40938: tektoncd pipeline · Argument Injection

Affects tektoncd pipelineSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High · fixed in 1.11.1 : patch tektoncd pipeline soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.11.1, 1.9.3, 1.6.2 +2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
tektoncdpipelineAffected
  • >=1.10.0 <1.11.1
Fixed in
  • 1.11.1
tektoncdpipelineAffected
  • >=1.7.0 <1.9.3
Fixed in
  • 1.9.3
tektoncdpipelineAffected
  • >=1.4.0 <1.6.2
Fixed in
  • 1.6.2
tektoncdpipelineAffected
  • >=1.2.0 <1.3.4
Fixed in
  • 1.3.4
tektoncdpipelineAffected
  • >=1.0.0 <1.0.2
Fixed in
  • 1.0.2
GitHubtektoncd/pipelinepkg:github/tektoncd/pipelineOther threatsAffected
  • <1.0.2
  • >=1.0.0 <1.3.4
  • >=1.3.4 <1.6.2
  • >=1.6.2 <1.9.3
  • >=1.9.3 <1.11.1
Fixed in
  • 1.0.2
  • 1.3.4
  • 1.6.2
  • 1.9.3
  • 1.11.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users are advised to upgrade to fixed versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, or 1.11.1 where the issue is resolved. If upgrading is not immediately possible, consider restricting the ability to submit ResolutionRequest objects to trusted users only, as exploitation requires authenticated access.

Description

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.

References

Community reviews

Loading reviews…