<?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://cve.radiocsirt.org</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, 06 Oct 2026 06:10:41 +0000</lastBuildDate>
    <item>
      <title>BIT-flux-2022-24877 — Improper path handling in kustomization files allows path traversal</title>
      <link>https://cve.radiocsirt.org/vuln/bit-flux-2022-24877</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: flux&lt;/p&gt;
&lt;p&gt;Flux is an open and extensible continuous delivery solution for Kubernetes. Path Traversal in the kustomize-controller via a malicious `kustomization.yaml` allows an attacker to expose sensitive data from the controller’s pod filesystem and possibly privilege escalation in multi-tenancy deployments. Workarounds include automated tooling in the user&amp;#39;s CI/CD pipeline to validate `kustomization.yaml` files conform with specific policies. This vulnerability is fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: flux&lt;/p&gt;
&lt;p&gt;Flux is an open and extensible continuous delivery solution for Kubernetes. Path Traversal in the kustomize-controller via a malicious `kustomization.yaml` allows an attacker to expose sensitive data from the controller’s pod filesystem and possibly privilege escalation in multi-tenancy deployments. Workarounds include automated tooling in the user&amp;#39;s CI/CD pipeline to validate `kustomization.yaml` files conform with specific policies. This vulnerability is fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-flux-2022-24877</guid>
    </item>
    <item>
      <title>EUVD-2026-234165</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-234165</link>
      <description>EUVD-2026-234165</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-234165</guid>
    </item>
    <item>
      <title>fkie_cve-2022-24877</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-24877</link>
      <description>&lt;p&gt;Flux is an open and extensible continuous delivery solution for Kubernetes. Path Traversal in the kustomize-controller via a malicious `kustomization.yaml` allows an attacker to expose sensitive data from the controller’s pod filesystem and possibly privilege escalation in multi-tenancy deployments. Workarounds include automated tooling in the user&amp;#39;s CI/CD pipeline to validate `kustomization.yaml` files conform with specific policies. This vulnerability is fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Flux is an open and extensible continuous delivery solution for Kubernetes. Path Traversal in the kustomize-controller via a malicious `kustomization.yaml` allows an attacker to expose sensitive data from the controller’s pod filesystem and possibly privilege escalation in multi-tenancy deployments. Workarounds include automated tooling in the user&amp;#39;s CI/CD pipeline to validate `kustomization.yaml` files conform with specific policies. This vulnerability is fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-24877</guid>
    </item>
    <item>
      <title>GHSA-j77r-2fxf-5jrw — Improper path handling in kustomization files allows path traversal</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j77r-2fxf-5jrw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/fluxcd/kustomize-controller, Go: github.com/fluxcd/flux2&lt;/p&gt;
&lt;p&gt;The kustomize-controller enables the use of Kustomize’s functionality when applying Kubernetes declarative state onto a cluster. A malicious user can use built-in features and a specially crafted `kustomization.yaml` to expose sensitive data from the controller’s pod filesystem. In multi-tenancy deployments this can lead to privilege escalation if the controller&amp;#39;s service account has elevated permissions.&lt;/p&gt;
&lt;p&gt;Within the affected versions, users with write access to a Flux source are able to use built-in features to expose sensitive data from the controller’s pod filesystem using a malicious `kustomization.yaml` file.&lt;/p&gt;
&lt;p&gt;This vulnerability was fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0 released on 2022-04-20. The changes introduce a new Kustomize file system implementation which ensures that all files being handled are contained within the Kustomization working directory, blocking references to any files that do not meet that requirement.&lt;/p&gt;
&lt;p&gt;Automated tooling (e.g. conftest) could be employed as a workaround, as part of a user&amp;#39;s CI/CD pipeline to ensure that their `kustomization.yaml` files conform with specific policies, blocking access to sensitive path locations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/fluxcd/kustomize-controller, Go: github.com/fluxcd/flux2&lt;/p&gt;
&lt;p&gt;The kustomize-controller enables the use of Kustomize’s functionality when applying Kubernetes declarative state onto a cluster. A malicious user can use built-in features and a specially crafted `kustomization.yaml` to expose sensitive data from the controller’s pod filesystem. In multi-tenancy deployments this can lead to privilege escalation if the controller&amp;#39;s service account has elevated permissions.&lt;/p&gt;
&lt;p&gt;Within the affected versions, users with write access to a Flux source are able to use built-in features to expose sensitive data from the controller’s pod filesystem using a malicious `kustomization.yaml` file.&lt;/p&gt;
&lt;p&gt;This vulnerability was fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0 released on 2022-04-20. The changes introduce a new Kustomize file system implementation which ensures that all files being handled are contained within the Kustomization working directory, blocking references to any files that do not meet that requirement.&lt;/p&gt;
&lt;p&gt;Automated tooling (e.g. conftest) could be employed as a workaround, as part of a user&amp;#39;s CI/CD pipeline to ensure that their `kustomization.yaml` files conform with specific policies, blocking access to sensitive path locations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j77r-2fxf-5jrw</guid>
    </item>
    <item>
      <title>gsd-2022-24877</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-24877</link>
      <description>gsd-2022-24877</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-24877</guid>
    </item>
  </channel>
</rss>
