<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 09:31:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-40938 — Tekton Pipelines: Git Resolver Unsanitized Revision Parameter Enables git Argument Injection Leading to RCE</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-40938</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tektoncd pipeline, Red Hat OpenShift Builds 1.7.3, Red Hat OpenShift Builds 1.8.1, Red Hat OpenShift Pipelines 1.21, Red Hat OpenShift Lightspeed, Red Hat OpenShift Pipelines, Red Hat OpenShift Serverless, Red Hat OpenShift AI (RHOAI), Red Hat OpenShift Virtualization 4, Red Hat Trusted Artifact Signer&lt;/p&gt;
&lt;p&gt;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&amp;#39;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=&amp;lt;binary&amp;gt;. 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tektoncd pipeline, Red Hat OpenShift Builds 1.7.3, Red Hat OpenShift Builds 1.8.1, Red Hat OpenShift Pipelines 1.21, Red Hat OpenShift Lightspeed, Red Hat OpenShift Pipelines, Red Hat OpenShift Serverless, Red Hat OpenShift AI (RHOAI), Red Hat OpenShift Virtualization 4, Red Hat Trusted Artifact Signer&lt;/p&gt;
&lt;p&gt;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&amp;#39;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=&amp;lt;binary&amp;gt;. 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-40938</guid>
    </item>
  </channel>
</rss>
