<?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://db.gcve.eu</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>Sat, 02 May 2026 03:29:32 +0000</lastBuildDate>
    <item>
      <title>8cf4a80f-1acb-4053-a3a7-c048c9d3fce5</title>
      <link>https://db.gcve.eu/sighting/8cf4a80f-1acb-4053-a3a7-c048c9d3fce5/export</link>
      <description>{"uuid": "8cf4a80f-1acb-4053-a3a7-c048c9d3fce5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "RHSA-2025:0648", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/6398", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-8676\n\ud83d\udd25 CVSS Score: 7.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N)\n\ud83d\udd39 Description: A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from the restore archive instead of the pod request. As a result, the validations run on the pod spec, verifying that the pod has access to the mounts it specifies are not applicable to a restored container. This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the restore.\n\ud83d\udccf Published: 2024-11-26T19:15:48.475Z\n\ud83d\udccf Modified: 2025-03-04T18:20:24.881Z\n\ud83d\udd17 References:\n1. https://access.redhat.com/errata/RHBA-2024:10826\n2. https://access.redhat.com/errata/RHSA-2025:0648\n3. https://access.redhat.com/errata/RHSA-2025:1908\n4. https://access.redhat.com/security/cve/CVE-2024-8676\n5. https://bugzilla.redhat.com/show_bug.cgi?id=2313842", "creation_timestamp": "2025-03-04T18:32:39.000000Z"}</description>
      <content:encoded>{"uuid": "8cf4a80f-1acb-4053-a3a7-c048c9d3fce5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "RHSA-2025:0648", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/6398", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-8676\n\ud83d\udd25 CVSS Score: 7.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N)\n\ud83d\udd39 Description: A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from the restore archive instead of the pod request. As a result, the validations run on the pod spec, verifying that the pod has access to the mounts it specifies are not applicable to a restored container. This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the restore.\n\ud83d\udccf Published: 2024-11-26T19:15:48.475Z\n\ud83d\udccf Modified: 2025-03-04T18:20:24.881Z\n\ud83d\udd17 References:\n1. https://access.redhat.com/errata/RHBA-2024:10826\n2. https://access.redhat.com/errata/RHSA-2025:0648\n3. https://access.redhat.com/errata/RHSA-2025:1908\n4. https://access.redhat.com/security/cve/CVE-2024-8676\n5. https://bugzilla.redhat.com/show_bug.cgi?id=2313842", "creation_timestamp": "2025-03-04T18:32:39.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/8cf4a80f-1acb-4053-a3a7-c048c9d3fce5/export</guid>
      <pubDate>Tue, 04 Mar 2025 18:32:39 +0000</pubDate>
    </item>
    <item>
      <title>61f095ae-1543-477a-b648-a332d2120a03</title>
      <link>https://db.gcve.eu/sighting/61f095ae-1543-477a-b648-a332d2120a03/export</link>
      <description>{"uuid": "61f095ae-1543-477a-b648-a332d2120a03", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "RHSA-2025:0648", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/10194", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-8676\n\ud83d\udd25 CVSS Score: 7.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N)\n\ud83d\udd39 Description: A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from the restore archive instead of the pod request. As a result, the validations run on the pod spec, verifying that the pod has access to the mounts it specifies are not applicable to a restored container. This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the restore.\n\ud83d\udccf Published: 2024-11-26T19:15:48.475Z\n\ud83d\udccf Modified: 2025-04-03T10:28:35.970Z\n\ud83d\udd17 References:\n1. https://access.redhat.com/errata/RHBA-2024:10826\n2. https://access.redhat.com/errata/RHSA-2025:0648\n3. https://access.redhat.com/errata/RHSA-2025:1908\n4. https://access.redhat.com/errata/RHSA-2025:3297\n5. https://access.redhat.com/security/cve/CVE-2024-8676\n6. https://bugzilla.redhat.com/show_bug.cgi?id=2313842", "creation_timestamp": "2025-04-03T10:35:13.000000Z"}</description>
      <content:encoded>{"uuid": "61f095ae-1543-477a-b648-a332d2120a03", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "RHSA-2025:0648", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/10194", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-8676\n\ud83d\udd25 CVSS Score: 7.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N)\n\ud83d\udd39 Description: A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from the restore archive instead of the pod request. As a result, the validations run on the pod spec, verifying that the pod has access to the mounts it specifies are not applicable to a restored container. This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the restore.\n\ud83d\udccf Published: 2024-11-26T19:15:48.475Z\n\ud83d\udccf Modified: 2025-04-03T10:28:35.970Z\n\ud83d\udd17 References:\n1. https://access.redhat.com/errata/RHBA-2024:10826\n2. https://access.redhat.com/errata/RHSA-2025:0648\n3. https://access.redhat.com/errata/RHSA-2025:1908\n4. https://access.redhat.com/errata/RHSA-2025:3297\n5. https://access.redhat.com/security/cve/CVE-2024-8676\n6. https://bugzilla.redhat.com/show_bug.cgi?id=2313842", "creation_timestamp": "2025-04-03T10:35:13.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/61f095ae-1543-477a-b648-a332d2120a03/export</guid>
      <pubDate>Thu, 03 Apr 2025 10:35:13 +0000</pubDate>
    </item>
  </channel>
</rss>
