<?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://db.gcve.eu</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, 10 Nov 2026 02:25:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-50240 — Pipelines-as-code: openshift-pipelines-operator-rh: pipelines-as-code: repository users can trigger namespace edit-equi…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-50240</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pipelines-as-code, Red Hat Builds for Red Hat OpenShift, Red Hat OpenShift Pipelines, Red Hat OpenShift Serverless, Red Hat OpenShift Dev Spaces, Red Hat Web Terminal&lt;/p&gt;
&lt;p&gt;A flaw was found in OpenShift Pipelines-as-Code (PAC). PAC does not verify whether the creator of a Repository custom resource has permission to create PipelineRuns. A namespace user with only Repository and Secret create/delete permissions can cause PAC to execute attacker-controlled PipelineRuns as the auto-provisioned pipeline ServiceAccount, which carries ClusterRole/edit by default. This results in namespace-scoped privilege escalation, enabling Secret read, resource creation/modification/deletion, and potential supply chain injection in CI/CD namespaces.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pipelines-as-code, Red Hat Builds for Red Hat OpenShift, Red Hat OpenShift Pipelines, Red Hat OpenShift Serverless, Red Hat OpenShift Dev Spaces, Red Hat Web Terminal&lt;/p&gt;
&lt;p&gt;A flaw was found in OpenShift Pipelines-as-Code (PAC). PAC does not verify whether the creator of a Repository custom resource has permission to create PipelineRuns. A namespace user with only Repository and Secret create/delete permissions can cause PAC to execute attacker-controlled PipelineRuns as the auto-provisioned pipeline ServiceAccount, which carries ClusterRole/edit by default. This results in namespace-scoped privilege escalation, enabling Secret read, resource creation/modification/deletion, and potential supply chain injection in CI/CD namespaces.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-50240</guid>
    </item>
  </channel>
</rss>
