CyberSecBulletin
CVE-2026-40938NVD status: Modified

pipeline: Improper Neutralization of Argument Delimiters in a Command

Published Updated By the CyberSecBulletin desk

CVE-2026-40938 is a high-severity improper neutralization of argument delimiters in a command vulnerability in pipeline from Tektoncd, with a CVSS 3.1 base score of 8.5 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected pipeline versions: >= 1.0.0, < 1.0.2; >= 1.2.0, < 1.3.4; >= 1.4.0, < 1.6.2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.79% chance of exploitation within 30 days, higher than 57% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Tekton Pipelines to 1.11.0 or a later version.
  2. Read the advisory on github.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Tektoncdpipeline>= 1.0.0, < 1.0.2; >= 1.2.0, < 1.3.4; >= 1.4.0, < 1.6.2; >= 1.7.0, < 1.9.3; >= 1.10.0, < 1.11.1Not stated
Red HatRed Hat OpenShift Builds 1.7.3Not specified in the recordNot stated
Red HatRed Hat OpenShift Builds 1.8.1Not specified in the recordNot stated
Red HatRed Hat OpenShift Pipelines 1.21Not specified in the recordNot stated
Red HatOpenShift LightspeedNot specified in the recordNot stated
Red HatOpenShift PipelinesNot specified in the recordNot stated
Red HatOpenShift ServerlessNot specified in the recordNot stated
Red HatRed Hat OpenShift AI (RHOAI)Not specified in the recordNot stated
Red HatRed Hat OpenShift Virtualization 4Not specified in the recordNot stated
Red HatRed Hat Trusted Artifact SignerNot specified in the recordNot stated
Linux FoundationTekton Pipelines1.0.0 up to, but not including, 1.11.01.11.0

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighCNA (github.com)
CVSS 3.18.5HighNVD
CVSS 3.18.5HighCNA

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Neutralization of Argument Delimiters in a Command

The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.

How developers prevent this class of flaw

  • Understand all the potential areas where untrusted inputs can enter your product: parameters or arguments, cookies, anything read from the network, environment variables, request headers as well as content, URL components, e-mail, files, databases, and any external systems that provide data to the application. Perform input validation at well-defined interfaces.
  • Directly convert your input type into the expected data type, such as using a conversion function that translates a string into a number. After converting to the expected data type, ensure that the input's values fall within the expected range of allowable values and that multi-field consistencies are maintained.
  • When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.

More Improper Neutralization of Argument Delimiters in a Command vulnerabilities (CWE-88)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Other vulnerabilities in pipeline

All pipeline vulnerabilities

Recent Improper Neutralization of Argument Delimiters in a Command vulnerabilities

Spotted an error? Tell us.