<?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 11:54:27 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-276195</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-276195</link>
      <description>EUVD-2026-276195</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-276195</guid>
    </item>
    <item>
      <title>fkie_cve-2026-32720</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32720</link>
      <description>&lt;p&gt;The CTFer.io Monitoring component is in charge of the collection, process and storage of various signals (i.e. logs, metrics and distributed traces). Prior to 0.2.1, due to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. This vulnerability is fixed in 0.2.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The CTFer.io Monitoring component is in charge of the collection, process and storage of various signals (i.e. logs, metrics and distributed traces). Prior to 0.2.1, due to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. This vulnerability is fixed in 0.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-32720</guid>
    </item>
    <item>
      <title>GHSA-7x23-j8gv-v54x — github.com/ctfer-io/monitoring Vulnerable to Improper Access Control</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7x23-j8gv-v54x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/ctfer-io/monitoring&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Due to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace.
This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement.&lt;/p&gt;
&lt;p&gt;### Patch&lt;/p&gt;
&lt;p&gt;Removing the `inter-ns` NetworkPolicy patches the vulnerability. If updates are not possible in production environments, we recommend to manually delete it and update as soon as possible.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;Given your context, delete the failing network policy that should be prefixed by `inter-ns-` in the monitoring namespace.
You can use the following to delete all matching network policy. If unsure of the outcome, please do it manually.&lt;/p&gt;
&lt;p&gt;```bash
for ns in $(kubectl get ns -o jsonpath=&amp;#39;{.items[*].metadata.name}&amp;#39; | tr &amp;#39; &amp;#39; &amp;#39;\n&amp;#39; | grep &amp;#39;^monitoring-&amp;#39;); do
  kubectl -n &amp;#34;$ns&amp;#34; get networkpolicy -o name \
  | grep &amp;#39;^networkpolicy.networking.k8s.io/inter-ns-&amp;#39; \
  | xargs -r kubectl -n &amp;#34;$ns&amp;#34; delete
done
```&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/ctfer-io/monitoring&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Due to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace.
This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement.&lt;/p&gt;
&lt;p&gt;### Patch&lt;/p&gt;
&lt;p&gt;Removing the `inter-ns` NetworkPolicy patches the vulnerability. If updates are not possible in production environments, we recommend to manually delete it and update as soon as possible.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;Given your context, delete the failing network policy that should be prefixed by `inter-ns-` in the monitoring namespace.
You can use the following to delete all matching network policy. If unsure of the outcome, please do it manually.&lt;/p&gt;
&lt;p&gt;```bash
for ns in $(kubectl get ns -o jsonpath=&amp;#39;{.items[*].metadata.name}&amp;#39; | tr &amp;#39; &amp;#39; &amp;#39;\n&amp;#39; | grep &amp;#39;^monitoring-&amp;#39;); do
  kubectl -n &amp;#34;$ns&amp;#34; get networkpolicy -o name \
  | grep &amp;#39;^networkpolicy.networking.k8s.io/inter-ns-&amp;#39; \
  | xargs -r kubectl -n &amp;#34;$ns&amp;#34; delete
done
```&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7x23-j8gv-v54x</guid>
    </item>
  </channel>
</rss>
