<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T11:17:19.102809+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2024-7598</id>
    <title>CVE-2024-7598 — Network restriction bypass via race condition during namespace termination</title>
    <updated>2026-10-02T11:17:19.152959+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Kubernetes kube-apiserver</p>
<p>A security issue was discovered in Kubernetes where a malicious or compromised pod could bypass network restrictions enforced by network policies during namespace deletion. The order in which objects are deleted during namespace termination is not defined, and it is possible for network policies to be deleted before the pods that they protect. This can lead to a brief period in which the pods are running, but network policies that should apply to connections to and from the pods are not enforced.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2024-7598"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4x4m-3c2p-qppc</id>
    <title>GHSA-4x4m-3c2p-qppc — Kubernetes Nodes can delete themselves by adding an OwnerReference</title>
    <updated>2026-10-02T11:17:19.153031+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: k8s.io/kubernetes</p>
<p>A vulnerability exists in the NodeRestriction admission controller in Kubernetes clusters where node users can delete their corresponding node object by patching themselves with an OwnerReference to a cluster-scoped resource. If the OwnerReference resource does not exist or is subsequently deleted, the given node object will be deleted via garbage collection.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4x4m-3c2p-qppc"/>
  </entry>
</feed>
