<?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>Wed, 07 Oct 2026 10:20:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-326969</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-326969</link>
      <description>EUVD-2026-326969</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-326969</guid>
    </item>
    <item>
      <title>fkie_cve-2026-47190</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47190</link>
      <description>&lt;p&gt;IPAM is the IP address Manager for Cluster API Provider Metal3. Prior to versions 1.11.7, 1.12.4, and 1.13.0, the IPAM controller&amp;#39;s ClusterRole granted full CRUD permissions (create, delete, get, list, patch, update, watch) on core/v1 Secrets. The controller never accesses Secrets during normal operation. If the controller pod were compromised (e.g. via supply chain attack or container escape), an attacker could leverage these excessive permissions to read, modify, or delete Secrets in the namespace, potentially exposing credentials and other sensitive data. This issue has been patched in versions 1.11.7, 1.12.4, and 1.13.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;IPAM is the IP address Manager for Cluster API Provider Metal3. Prior to versions 1.11.7, 1.12.4, and 1.13.0, the IPAM controller&amp;#39;s ClusterRole granted full CRUD permissions (create, delete, get, list, patch, update, watch) on core/v1 Secrets. The controller never accesses Secrets during normal operation. If the controller pod were compromised (e.g. via supply chain attack or container escape), an attacker could leverage these excessive permissions to read, modify, or delete Secrets in the namespace, potentially exposing credentials and other sensitive data. This issue has been patched in versions 1.11.7, 1.12.4, and 1.13.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-47190</guid>
    </item>
    <item>
      <title>GHSA-49pm-43hf-6xfq — IPAM controller service account granted unnecessary full access to Secrets</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-49pm-43hf-6xfq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/metal3-io/ip-address-manager&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;IPAM is the IP address Manager for Cluster API Provider Metal3. The IPAM controller&amp;#39;s ClusterRole granted full CRUD permissions (create, delete, get, list, patch, update, watch) on core/v1 Secrets. The controller never accesses Secrets during normal operation. If the controller pod were compromised (e.g. via supply chain attack or container escape), an attacker could leverage these excessive  permissions to read, modify, or delete Secrets in the namespace, potentially exposing credentials and other sensitive data.&lt;/p&gt;
&lt;p&gt;All users running ip-address-manager versions prior to the patched releases are affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in:
- v1.11.7
- v1.12.4
- v1.13.0&lt;/p&gt;
&lt;p&gt;Users should upgrade to the patched version for their release branch.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Manually remove the Secrets resource entry from the metal3-ipam-controller-manager-role ClusterRole:&lt;/p&gt;
&lt;p&gt;```yaml
# Remove this entire block from the ClusterRole
- apiGroups:
  - &amp;#34;&amp;#34;
  resources:
  - secrets
  verbs:
  - create
  - delete
  - get
  - list
  - patch
  - update
  - watch
```&lt;/p&gt;
&lt;p&gt;### Resources&lt;/p&gt;
&lt;p&gt;- https://github.com/metal3-io/ip-address-manager/pull/1355
- https://github.com/metal3-io/ip-address-manager/pull/1356 (backport to release-1.12)
- https://github.com/metal3-io/ip-address-manager/pull/1357 (backport to release-1.11)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/metal3-io/ip-address-manager&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;IPAM is the IP address Manager for Cluster API Provider Metal3. The IPAM controller&amp;#39;s ClusterRole granted full CRUD permissions (create, delete, get, list, patch, update, watch) on core/v1 Secrets. The controller never accesses Secrets during normal operation. If the controller pod were compromised (e.g. via supply chain attack or container escape), an attacker could leverage these excessive  permissions to read, modify, or delete Secrets in the namespace, potentially exposing credentials and other sensitive data.&lt;/p&gt;
&lt;p&gt;All users running ip-address-manager versions prior to the patched releases are affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in:
- v1.11.7
- v1.12.4
- v1.13.0&lt;/p&gt;
&lt;p&gt;Users should upgrade to the patched version for their release branch.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Manually remove the Secrets resource entry from the metal3-ipam-controller-manager-role ClusterRole:&lt;/p&gt;
&lt;p&gt;```yaml
# Remove this entire block from the ClusterRole
- apiGroups:
  - &amp;#34;&amp;#34;
  resources:
  - secrets
  verbs:
  - create
  - delete
  - get
  - list
  - patch
  - update
  - watch
```&lt;/p&gt;
&lt;p&gt;### Resources&lt;/p&gt;
&lt;p&gt;- https://github.com/metal3-io/ip-address-manager/pull/1355
- https://github.com/metal3-io/ip-address-manager/pull/1356 (backport to release-1.12)
- https://github.com/metal3-io/ip-address-manager/pull/1357 (backport to release-1.11)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-49pm-43hf-6xfq</guid>
    </item>
  </channel>
</rss>
