<?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, 13 Oct 2026 23:22:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-103413 — Apache Camel Karavan: unvalidated Kubernetes resources applied from a project's kubernetes.yaml</title>
      <link>https://db.gcve.eu/vuln/cve-2026-103413</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Camel Karavan&lt;/p&gt;
&lt;p&gt;Improper input validation vulnerability in Apache Camel Karavan.&lt;/p&gt;
&lt;p&gt;When a deployment was started, Karavan unmarshalled a project&amp;#39;s `kubernetes.yaml` and applied every resource it contained to the cluster without restricting the resource kinds, without rejecting security-sensitive pod options, and without pinning the target namespace. An authenticated user of any role could therefore have Karavan apply arbitrary Kubernetes resources within the reach of its service account, including pods requesting hostNetwork, hostPID, hostIPC, hostPath volumes, host ports, privileged containers, privilege escalation or added capabilities.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Camel Karavan: from 4.0.0 before 4.22.1.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 4.22.1, which fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Camel Karavan&lt;/p&gt;
&lt;p&gt;Improper input validation vulnerability in Apache Camel Karavan.&lt;/p&gt;
&lt;p&gt;When a deployment was started, Karavan unmarshalled a project&amp;#39;s `kubernetes.yaml` and applied every resource it contained to the cluster without restricting the resource kinds, without rejecting security-sensitive pod options, and without pinning the target namespace. An authenticated user of any role could therefore have Karavan apply arbitrary Kubernetes resources within the reach of its service account, including pods requesting hostNetwork, hostPID, hostIPC, hostPath volumes, host ports, privileged containers, privilege escalation or added capabilities.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Camel Karavan: from 4.0.0 before 4.22.1.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 4.22.1, which fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-103413</guid>
    </item>
  </channel>
</rss>
