<?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 sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 10 Jun 2026 00:26:19 +0000</lastBuildDate>
    <item>
      <title>3a734535-472e-4d70-8339-c55923965f2c</title>
      <link>https://vulnerability.circl.lu/sighting/3a734535-472e-4d70-8339-c55923965f2c/export</link>
      <description>{"uuid": "3a734535-472e-4d70-8339-c55923965f2c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7598", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/8238", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-7598\n\ud83d\udd25 CVSS Score: 3.1 (cvssV3_1, Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\ud83d\udd39 Description: 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.\n\ud83d\udccf Published: 2025-03-20T16:52:57.929Z\n\ud83d\udccf Modified: 2025-03-20T16:52:57.929Z\n\ud83d\udd17 References:\n1. https://github.com/kubernetes/kubernetes/issues/126587\n2. https://groups.google.com/g/kubernetes-security-announce/c/67D7UFqiPRc", "creation_timestamp": "2025-03-20T17:18:46.000000Z"}</description>
      <content:encoded>{"uuid": "3a734535-472e-4d70-8339-c55923965f2c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7598", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/8238", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-7598\n\ud83d\udd25 CVSS Score: 3.1 (cvssV3_1, Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\ud83d\udd39 Description: 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.\n\ud83d\udccf Published: 2025-03-20T16:52:57.929Z\n\ud83d\udccf Modified: 2025-03-20T16:52:57.929Z\n\ud83d\udd17 References:\n1. https://github.com/kubernetes/kubernetes/issues/126587\n2. https://groups.google.com/g/kubernetes-security-announce/c/67D7UFqiPRc", "creation_timestamp": "2025-03-20T17:18:46.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/3a734535-472e-4d70-8339-c55923965f2c/export</guid>
      <pubDate>Thu, 20 Mar 2025 17:18:46 +0000</pubDate>
    </item>
    <item>
      <title>439c1f36-f814-4506-9725-ff6a1e4588fd</title>
      <link>https://vulnerability.circl.lu/sighting/439c1f36-f814-4506-9725-ff6a1e4588fd/export</link>
      <description>{"uuid": "439c1f36-f814-4506-9725-ff6a1e4588fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7598", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3lktfkgalqy2j", "content": "", "creation_timestamp": "2025-03-20T19:09:33.450747Z"}</description>
      <content:encoded>{"uuid": "439c1f36-f814-4506-9725-ff6a1e4588fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7598", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3lktfkgalqy2j", "content": "", "creation_timestamp": "2025-03-20T19:09:33.450747Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/439c1f36-f814-4506-9725-ff6a1e4588fd/export</guid>
      <pubDate>Thu, 20 Mar 2025 19:09:33 +0000</pubDate>
    </item>
    <item>
      <title>010b6834-c1c6-44c3-9cdf-524427adcf97</title>
      <link>https://vulnerability.circl.lu/sighting/010b6834-c1c6-44c3-9cdf-524427adcf97/export</link>
      <description>{"uuid": "010b6834-c1c6-44c3-9cdf-524427adcf97", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7598", "type": "seen", "source": "https://t.me/cvedetector/20754", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-7598 - Kubernetes Namespace Deletion Network Policy Bypass\", \n  \"Content\": \"CVE ID : CVE-2024-7598 \nPublished : March 20, 2025, 5:15 p.m. | 55\u00a0minutes ago \nDescription : 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. \nSeverity: 3.1 | LOW \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"20 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-20T19:54:37.000000Z"}</description>
      <content:encoded>{"uuid": "010b6834-c1c6-44c3-9cdf-524427adcf97", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7598", "type": "seen", "source": "https://t.me/cvedetector/20754", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-7598 - Kubernetes Namespace Deletion Network Policy Bypass\", \n  \"Content\": \"CVE ID : CVE-2024-7598 \nPublished : March 20, 2025, 5:15 p.m. | 55\u00a0minutes ago \nDescription : 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. \nSeverity: 3.1 | LOW \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"20 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-20T19:54:37.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/010b6834-c1c6-44c3-9cdf-524427adcf97/export</guid>
      <pubDate>Thu, 20 Mar 2025 19:54:37 +0000</pubDate>
    </item>
    <item>
      <title>a01c1f6d-cc93-471f-9e1c-5f643eaeb5a3</title>
      <link>https://vulnerability.circl.lu/sighting/a01c1f6d-cc93-471f-9e1c-5f643eaeb5a3/export</link>
      <description>{"uuid": "a01c1f6d-cc93-471f-9e1c-5f643eaeb5a3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7598", "type": "seen", "source": "https://bsky.app/profile/buherator.bsky.social/post/3lktja6n3yr2r", "content": "", "creation_timestamp": "2025-03-20T20:15:25.531054Z"}</description>
      <content:encoded>{"uuid": "a01c1f6d-cc93-471f-9e1c-5f643eaeb5a3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7598", "type": "seen", "source": "https://bsky.app/profile/buherator.bsky.social/post/3lktja6n3yr2r", "content": "", "creation_timestamp": "2025-03-20T20:15:25.531054Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/a01c1f6d-cc93-471f-9e1c-5f643eaeb5a3/export</guid>
      <pubDate>Thu, 20 Mar 2025 20:15:25 +0000</pubDate>
    </item>
    <item>
      <title>34a3c514-48c7-41a2-a471-dee018c80247</title>
      <link>https://vulnerability.circl.lu/sighting/34a3c514-48c7-41a2-a471-dee018c80247/export</link>
      <description>{"uuid": "34a3c514-48c7-41a2-a471-dee018c80247", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7598", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lktlxadbpp2w", "content": "", "creation_timestamp": "2025-03-20T21:04:06.972483Z"}</description>
      <content:encoded>{"uuid": "34a3c514-48c7-41a2-a471-dee018c80247", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-7598", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lktlxadbpp2w", "content": "", "creation_timestamp": "2025-03-20T21:04:06.972483Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/34a3c514-48c7-41a2-a471-dee018c80247/export</guid>
      <pubDate>Thu, 20 Mar 2025 21:04:06 +0000</pubDate>
    </item>
  </channel>
</rss>
