<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security-Advisory on Kubewarden</title><link>https://www.kubewarden.io/types/security-advisory/</link><description>Recent content in Security-Advisory on Kubewarden</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 21 Sep 2026 13:56:55 +0200</lastBuildDate><atom:link href="https://www.kubewarden.io/types/security-advisory/index.xml" rel="self" type="application/rss+xml"/><item><title>Admission controller 1.37.2 Release</title><link>https://www.kubewarden.io/blog/2026/08/admission-controller-1.37.2-release/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.kubewarden.io/blog/2026/08/admission-controller-1.37.2-release/</guid><description>&lt;p&gt;Hi all! This patch release ships several fixes for the community. One of them&#10;addresses a CVE, and the others fix usability issues in the secure supply chain&#10;features and improve how Gatekeeper Rego runtime handle errors without&#10;representing an actual security failure.&lt;/p&gt;&#10;&lt;h2 id="admissionpolicy-unique-name-collision-enables-cross-namespace-webhook-confusion"&gt;AdmissionPolicy unique-name collision enables cross-namespace webhook confusion&lt;/h2&gt;&#10;&lt;p&gt;Community security researcher &lt;a href="https://github.com/thevilledev"&gt;Ville Vesilehto&lt;/a&gt;&#10;found a&#10;&lt;a href="https://github.com/kubewarden/adm-controller/security/advisories/GHSA-m5vp-9g65-pv6v"&gt;problem&lt;/a&gt;&#10;while testing Kubewarden&amp;rsquo;s namespaced admission policies. These policies should&#10;only evaluate resources in their own namespace. Ville&amp;rsquo;s finding shows that&#10;wasn&amp;rsquo;t always true.&lt;/p&gt;</description></item><item><title>Admission Controller 1.37 Release</title><link>https://www.kubewarden.io/blog/2026/07/admission-controller-1.37-release/</link><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.kubewarden.io/blog/2026/07/admission-controller-1.37-release/</guid><description>&lt;p&gt;Here we are, at the tail end of July. Belugas are migrating up north for the&#10;season, green turtles are moving to the islands for nesting, and spawned&#10;sardines are moving up the east coast of Africa. Kubewarden doesn&amp;rsquo;t want to&#10;miss this season!&lt;/p&gt;&#10;&lt;h2 id="migration-to-new-single-helm-chart-admission-controller-600"&gt;Migration to new single Helm chart admission-controller-6.0.0&lt;/h2&gt;&#10;&lt;p&gt;Since its inception, the Kubewarden Admission Controller has shipped as 3&#10;separate Helm charts: &lt;code&gt;kubewarden-crds&lt;/code&gt;, &lt;code&gt;kubewarden-controller&lt;/code&gt;, and&#10;&lt;code&gt;kubewarden-defaults&lt;/code&gt;.&lt;/p&gt;&#10;&lt;p&gt;This was done for flexibility: it allowed cluster operators to&#10;install/uninstall CRDs, recommended policies and PolicyServers on its own, and&#10;bump each part of the stack separately.&lt;/p&gt;</description></item><item><title>Admission Controller 1.35 Release</title><link>https://www.kubewarden.io/blog/2026/04/adm-controller-1.35-release/</link><pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.kubewarden.io/blog/2026/04/adm-controller-1.35-release/</guid><description>&lt;p&gt;This Admission Controller 1.35 release is one that builds the nest properly:&#10;load-bearing branches first, then careful weaving. A moderate security&#10;vulnerability has been fixed, and rather than a quick twig stuffed in a gap,&#10;the team reinforced the whole structure. This release brings also a new policy,&#10;an expansion on our threat model, and a JavaScrypt/TypeScrypt SDK relocation.&lt;/p&gt;&#10;&lt;h2 id="security-fix-rbac-reconnaissance-and-host-capability-calls"&gt;Security fix: RBAC reconnaissance and host capability calls&lt;/h2&gt;&#10;&lt;p&gt;Kubewarden makes the following security promise:&lt;/p&gt;</description></item><item><title>Admission Controller 1.33 Release</title><link>https://www.kubewarden.io/blog/2026/03/adm-controller-1.33-release/</link><pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.kubewarden.io/blog/2026/03/adm-controller-1.33-release/</guid><description>&lt;p&gt;The garden is thriving and Kubewarden 1.33 is ready to bloom! Following last&#10;release&amp;rsquo;s big repotting, this one is serious about pruning, including a&#10;security issue. It&amp;rsquo;s not all housekeeping though, fresh flowers are blooming&#10;and come with nice features: BYO-PKI landing in the policy-server, field mask&#10;filtering for context-aware calls, proxy support, and a few more treats. Let&amp;rsquo;s&#10;dig in!&lt;/p&gt;&#10;&lt;h2 id="security-fix-cross-namespace-data-access-removal-of-deprecated-api-calls"&gt;Security fix: Cross-namespace data access, removal of deprecated API calls&lt;/h2&gt;&#10;&lt;p&gt;In our &lt;a href="https://www.kubewarden.io/blog/2026/02/not-affected-by-cve-2026-22039/"&gt;previous&#10;post&lt;/a&gt;&#10;we explained how our architecture protects namespaced policy users from&#10;privilege escalations. While this still stands, Ville Vesilehto&#10;(&lt;a href="https://github.com/thevilledev"&gt;thevilledev&lt;/a&gt; on GitHub) found the following&#10;&lt;a href="https://github.com/kubewarden/kubewarden-controller/security/advisories/GHSA-6r7f-3fwq-hq74"&gt;security vulnerability&lt;/a&gt;: an attacker with permissions to create&#10;AdmissionPolicies could make use of 3 deprecated host-callbacks&#10;(&lt;code&gt;kubernetes/ingresses&lt;/code&gt;, &lt;code&gt;kubernetes/namespaces&lt;/code&gt;, &lt;code&gt;kubernetes/services&lt;/code&gt;) to&#10;craft a policy that would allow them read access to Ingresses, Namespaces, and&#10;Services resources respectively.&lt;/p&gt;</description></item><item><title>Not affected by cross-ns privilege escalation via policy api call</title><link>https://www.kubewarden.io/blog/2026/02/not-affected-by-cve-2026-22039/</link><pubDate>Mon, 16 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.kubewarden.io/blog/2026/02/not-affected-by-cve-2026-22039/</guid><description>&lt;h2 id="why-kubewarden-is-not-affected-by-cve-2026-22039"&gt;Why Kubewarden is not affected by CVE-2026-22039&lt;/h2&gt;&#10;&lt;p&gt;The recent vulnerability&#10;&lt;a href="https://nvd.nist.gov/vuln/detail/cve-2026-22039"&gt;CVE-2026-22039&lt;/a&gt; is doing the&#10;rounds in the Kubernetes security community, with dramatic titles such as &lt;em&gt;&amp;ldquo;How&#10;an admission controller vulnerability turned Kubernetes namespaces into a&#10;security illusion&amp;rdquo;&lt;/em&gt;. You can read about people doubting admission&#10;controllers, claiming they have too much power, or they represent too high a value&#10;target.&lt;/p&gt;&#10;&lt;p&gt;In this blogpost, we reassure Kubewarden users that they aren&amp;rsquo;t affected&#10;thanks to our architecture, and explain why.&lt;/p&gt;</description></item><item><title>Kubewarden 1.24 release</title><link>https://www.kubewarden.io/blog/2025/04/kubewarden-1.24-release/</link><pubDate>Wed, 30 Apr 2025 00:00:00 +0000</pubDate><guid>https://www.kubewarden.io/blog/2025/04/kubewarden-1.24-release/</guid><description>&lt;p&gt;The wait is over, Kubewarden 1.24 has arrived! We have some Easter eggs for you&#10;in this one.&lt;/p&gt;&#10;&lt;h2 id="promoting-our-policies-to-v100"&gt;Promoting our policies to v1.0.0&lt;/h2&gt;&#10;&lt;p&gt;In the past, we consciously picked semver &lt;code&gt;0.X.Y&lt;/code&gt; for policy versions as that&#10;meant that the policy API for the user (in this case, the policy&#10;&lt;code&gt;spec.settings&lt;/code&gt;) was not considered stable.&lt;/p&gt;&#10;&lt;p&gt;Since the settings of our policies haven&amp;rsquo;t changed since their initial release,&#10;we decided it was time to highlight their stability by promoting them to &lt;code&gt;v1.0.0&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Ingress-nginx CVE-2025-1974 - how Kubewarden can help you</title><link>https://www.kubewarden.io/blog/2025/04/ingress-nginx-cve-2025-1974/</link><pubDate>Thu, 03 Apr 2025 00:00:00 +0000</pubDate><guid>https://www.kubewarden.io/blog/2025/04/ingress-nginx-cve-2025-1974/</guid><description>&lt;p&gt;Last week, a high severity issue &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2025-1974"&gt;CVE-2025-1974&lt;/a&gt;&#10;was found affecting ingress-nginx, one of the most used ingress solutions for Kubernetes.&lt;/p&gt;&#10;&lt;h2 id="the-issue"&gt;The issue&lt;/h2&gt;&#10;&lt;p&gt;The issue allows an attacker to execute arbitrary code in the Pod running the&#10;controller. The attacker can then steal the Kubernetes identity of the nginx-ingress&#10;controller which, by design, has access to all the Secrets defined in the cluster.&lt;/p&gt;&#10;&lt;p&gt;The issue is exploited by making http requests against the validating webhook server used&#10;by the nginx-ingress controller. Only the Kubernetes API server should be allowed to make&#10;requests against the webhook endpoint.&#10;However, it was discovered that certain clusters are even exposing this webhook endpoint&#10;outside of the cluster, for example by using an &lt;code&gt;Ingress&lt;/code&gt; resource.&lt;/p&gt;</description></item><item><title>Kubewarden 1.21 release</title><link>https://www.kubewarden.io/blog/2025/01/kubewarden-1-21-release/</link><pubDate>Thu, 30 Jan 2025 00:00:00 +0000</pubDate><guid>https://www.kubewarden.io/blog/2025/01/kubewarden-1-21-release/</guid><description>&lt;p&gt;We&amp;rsquo;re excited to announce the release of Kubewarden v1.21, our first release of 2025!&lt;/p&gt;&#10;&lt;p&gt;The release addresses two security issues that the Kubewarden team has discovered. Detailed information about them is included below.&#10;While these issues do not have a critical impact, we recommend our users upgrade their Kubewarden deployments.&lt;/p&gt;&#10;&lt;p&gt;Alongside these security fixes, the 1.21 release includes the usual stream of dependency updates and features some improvements to our documentation.&lt;/p&gt;</description></item><item><title>Kubewarden 1.16 release</title><link>https://www.kubewarden.io/blog/2024/08/kubewarden-1-16-release/</link><pubDate>Mon, 19 Aug 2024 00:00:00 +0000</pubDate><guid>https://www.kubewarden.io/blog/2024/08/kubewarden-1-16-release/</guid><description>&lt;p&gt;We are thrilled to announce the release of Kubewarden v1.16.0! Following the&#10;northern hemisphere summer, this version packs some goodies but is a bit more&#10;lightweight than usual.&lt;/p&gt;&#10;&lt;h2 id="kwctl-scaffold-for-admissionrequests"&gt;kwctl scaffold for AdmissionRequests&lt;/h2&gt;&#10;&lt;p&gt;The &lt;code&gt;kwctl&lt;/code&gt; cli has learned a new command, &lt;code&gt;kwctl scaffold admission-request&lt;/code&gt;,&#10;which prints a Kubernetes AdmissionRequest object from the provided Kubernetes&#10;resource definition.&lt;/p&gt;&#10;&lt;p&gt;This is useful when developing policies (and not only limited to Kubewarden ones). Now,&#10;you can scaffold the desired AdmissionRequest the policy would receive, and&#10;then end-to-end test a Kubewarden policy against the created AdmissionRequest with&#10;&lt;code&gt;kwctl run&lt;/code&gt;. For example, here we scaffold a request to create an Ingress object,&#10;which then we use to test one of our policies out of cluster:&lt;/p&gt;</description></item><item><title>Kubewarden 1.6.0 is released!</title><link>https://www.kubewarden.io/blog/2023/04/kubewarden-.1.6.0-release/</link><pubDate>Mon, 17 Apr 2023 00:00:00 +0000</pubDate><guid>https://www.kubewarden.io/blog/2023/04/kubewarden-.1.6.0-release/</guid><description>&lt;p&gt;We are pleased to announce the availability of the Kubewarden 1.6.0 stack.&lt;/p&gt;&#10;&lt;p&gt;This release brings stability, performance and security improvements. All packed&#10;with a new major feature. Let&amp;rsquo;s dig into the changes!&lt;/p&gt;&#10;&lt;h2 id="security-improvements"&gt;Security Improvements&lt;/h2&gt;&#10;&lt;p&gt;The Kubewarden controller is ran using a dedicated Service Account. Prior to this&#10;release, the Service Account had access to a series of Kubernetes resources&#10;across the entire cluster.&lt;/p&gt;&#10;&lt;p&gt;Starting from this release, the Kubewarden controller Service Account has a&#10;more limited access to the cluster. Access to some resources is now tied to&#10;the Namespace inside of which the controller is deployed.&lt;/p&gt;</description></item><item><title>CRI-O CVE-2022-0811 Mitigation</title><link>https://www.kubewarden.io/blog/2022/03/cri-o-cve-mitigation/</link><pubDate>Tue, 29 Mar 2022 00:00:00 +0000</pubDate><guid>https://www.kubewarden.io/blog/2022/03/cri-o-cve-mitigation/</guid><description>&lt;p&gt;Recently a severe &lt;a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0811"&gt;CVE&lt;/a&gt;&#10;in the CRI-O container engine come to public. The flaw in CRI-O allows bad&#10;actors to gain root access and run arbitrary code in the host machine.&lt;/p&gt;&#10;&lt;p&gt;A &lt;a href="https://github.com/cri-o/cri-o/releases/tag/v1.23.2"&gt;fix&lt;/a&gt; for the issue is&#10;already available and you should update your cluster to avoid any headache in&#10;the future. But if you cannot do that right away, use Kubewarden to mitigate the impact of&#10;this issue. It&amp;rsquo;s possible to prevent pods with &lt;code&gt;sysctl&lt;/code&gt; configuration&#10;to run in the cluster with the policy &lt;code&gt;sysctl-psp&lt;/code&gt; available in the &lt;a href="https://hub.kubewarden.io/"&gt;Policy&#10;Hub&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>