<?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>Wed, 30 Sep 2026 00:44:57 +0000</lastBuildDate>
    <item>
      <title>GHSA-qjvc-p88j-j9rm — Kyverno's PolicyException objects can be created in any namespace by default</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-qjvc-p88j-j9rm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/kyverno/kyverno&lt;/p&gt;
&lt;p&gt;### Summary
A kyverno ClusterPolicy, ie. &amp;#34;disallow-privileged-containers,&amp;#34; can be overridden by the creation of a PolicyException in a random namespace.&lt;/p&gt;
&lt;p&gt;### Details
By design, PolicyExceptions are consumed from any namespace. Administrators may not recognize that this allows users with privileges to non-kyverno namespaces to create exceptions.&lt;/p&gt;
&lt;p&gt;### PoC
1. Administrator creates &amp;#34;disallow-privileged-containers&amp;#34; ClusterPolicy that applies to resources in the namespace &amp;#34;ubuntu-restricted&amp;#34;
2. Cluster user creates a PolicyException object for &amp;#34;disallow-privileged-containers&amp;#34; in namespace &amp;#34;ubuntu-restricted&amp;#34;
3. Cluster user creates a pod with a privileged container in &amp;#34;ubuntu-restricted&amp;#34; 
4. Cluster user escalates to root on the node from the privileged container&lt;/p&gt;
&lt;p&gt;### Impact
Administrators attempting to enforce cluster security through kyverno policies, but that allow less privileged users to create resources&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/kyverno/kyverno&lt;/p&gt;
&lt;p&gt;### Summary
A kyverno ClusterPolicy, ie. &amp;#34;disallow-privileged-containers,&amp;#34; can be overridden by the creation of a PolicyException in a random namespace.&lt;/p&gt;
&lt;p&gt;### Details
By design, PolicyExceptions are consumed from any namespace. Administrators may not recognize that this allows users with privileges to non-kyverno namespaces to create exceptions.&lt;/p&gt;
&lt;p&gt;### PoC
1. Administrator creates &amp;#34;disallow-privileged-containers&amp;#34; ClusterPolicy that applies to resources in the namespace &amp;#34;ubuntu-restricted&amp;#34;
2. Cluster user creates a PolicyException object for &amp;#34;disallow-privileged-containers&amp;#34; in namespace &amp;#34;ubuntu-restricted&amp;#34;
3. Cluster user creates a pod with a privileged container in &amp;#34;ubuntu-restricted&amp;#34; 
4. Cluster user escalates to root on the node from the privileged container&lt;/p&gt;
&lt;p&gt;### Impact
Administrators attempting to enforce cluster security through kyverno policies, but that allow less privileged users to create resources&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-qjvc-p88j-j9rm</guid>
    </item>
  </channel>
</rss>
