<?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>Thu, 23 Jul 2026 04:33:04 +0000</lastBuildDate>
    <item>
      <title>21c2c1fa-7979-4874-91e1-93b4ea6c1a6a</title>
      <link>https://vulnerability.circl.lu/sighting/21c2c1fa-7979-4874-91e1-93b4ea6c1a6a/export</link>
      <description>{"uuid": "21c2c1fa-7979-4874-91e1-93b4ea6c1a6a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56719", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/debian-linux-kernel-multiple-vulnerabilities_20260506", "content": "", "creation_timestamp": "2026-05-05T20:00:00.000000Z"}</description>
      <content:encoded>{"uuid": "21c2c1fa-7979-4874-91e1-93b4ea6c1a6a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56719", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/debian-linux-kernel-multiple-vulnerabilities_20260506", "content": "", "creation_timestamp": "2026-05-05T20:00:00.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/21c2c1fa-7979-4874-91e1-93b4ea6c1a6a/export</guid>
      <pubDate>Tue, 05 May 2026 20:00:00 +0000</pubDate>
    </item>
    <item>
      <title>110e6705-2131-4288-bd47-b34fe96fe2e5</title>
      <link>https://vulnerability.circl.lu/sighting/110e6705-2131-4288-bd47-b34fe96fe2e5/export</link>
      <description>{"uuid": "110e6705-2131-4288-bd47-b34fe96fe2e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56717", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}</description>
      <content:encoded>{"uuid": "110e6705-2131-4288-bd47-b34fe96fe2e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56717", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/110e6705-2131-4288-bd47-b34fe96fe2e5/export</guid>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>a71b17ab-5a92-4948-8533-501ee53c8923</title>
      <link>https://vulnerability.circl.lu/sighting/a71b17ab-5a92-4948-8533-501ee53c8923/export</link>
      <description>{"uuid": "a71b17ab-5a92-4948-8533-501ee53c8923", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56718", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}</description>
      <content:encoded>{"uuid": "a71b17ab-5a92-4948-8533-501ee53c8923", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56718", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/a71b17ab-5a92-4948-8533-501ee53c8923/export</guid>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>7a6d85aa-328b-494c-b071-89f91113160f</title>
      <link>https://vulnerability.circl.lu/sighting/7a6d85aa-328b-494c-b071-89f91113160f/export</link>
      <description>{"uuid": "7a6d85aa-328b-494c-b071-89f91113160f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56712", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}</description>
      <content:encoded>{"uuid": "7a6d85aa-328b-494c-b071-89f91113160f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56712", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/7a6d85aa-328b-494c-b071-89f91113160f/export</guid>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>91776a31-7716-403a-bc5d-f54b50f680d7</title>
      <link>https://vulnerability.circl.lu/sighting/91776a31-7716-403a-bc5d-f54b50f680d7/export</link>
      <description>{"uuid": "91776a31-7716-403a-bc5d-f54b50f680d7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56719", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}</description>
      <content:encoded>{"uuid": "91776a31-7716-403a-bc5d-f54b50f680d7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56719", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/91776a31-7716-403a-bc5d-f54b50f680d7/export</guid>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>8dc33e75-a521-4bbc-8abc-5da2f833dd02</title>
      <link>https://vulnerability.circl.lu/sighting/8dc33e75-a521-4bbc-8abc-5da2f833dd02/export</link>
      <description>{"uuid": "8dc33e75-a521-4bbc-8abc-5da2f833dd02", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56712", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}</description>
      <content:encoded>{"uuid": "8dc33e75-a521-4bbc-8abc-5da2f833dd02", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56712", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/8dc33e75-a521-4bbc-8abc-5da2f833dd02/export</guid>
      <pubDate>Wed, 03 Dec 2025 14:14:49 +0000</pubDate>
    </item>
    <item>
      <title>012926f5-ad5f-4cec-9089-feff829589e8</title>
      <link>https://vulnerability.circl.lu/sighting/012926f5-ad5f-4cec-9089-feff829589e8/export</link>
      <description>{"uuid": "012926f5-ad5f-4cec-9089-feff829589e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56718", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113736078642861422", "content": "", "creation_timestamp": "2024-12-29T12:20:33.601239Z"}</description>
      <content:encoded>{"uuid": "012926f5-ad5f-4cec-9089-feff829589e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56718", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113736078642861422", "content": "", "creation_timestamp": "2024-12-29T12:20:33.601239Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/012926f5-ad5f-4cec-9089-feff829589e8/export</guid>
      <pubDate>Sun, 29 Dec 2024 12:20:33 +0000</pubDate>
    </item>
    <item>
      <title>fb15a5f4-bd14-4c91-9d07-ac260b1824e7</title>
      <link>https://vulnerability.circl.lu/sighting/fb15a5f4-bd14-4c91-9d07-ac260b1824e7/export</link>
      <description>{"uuid": "fb15a5f4-bd14-4c91-9d07-ac260b1824e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56710", "type": "seen", "source": "https://t.me/cvedetector/13872", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56710 - Ceph Linux Kernel Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56710 \nPublished : Dec. 29, 2024, 9:15 a.m. | 24\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nceph: fix memory leak in ceph_direct_read_write()  \n  \nThe bvecs array which is allocated in iter_get_bvecs_alloc() is leaked  \nand pages remain pinned if ceph_alloc_sparse_ext_map() fails.  \n  \nThere is no need to delay the allocation of sparse_ext map until after  \nthe bvecs array is set up, so fix this by moving sparse_ext allocation  \na bit earlier.  Also, make a similar adjustment in __ceph_sync_read()  \nfor consistency (a leak of the same kind in __ceph_sync_read() has been  \naddressed differently). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T10:41:24.000000Z"}</description>
      <content:encoded>{"uuid": "fb15a5f4-bd14-4c91-9d07-ac260b1824e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56710", "type": "seen", "source": "https://t.me/cvedetector/13872", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56710 - Ceph Linux Kernel Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56710 \nPublished : Dec. 29, 2024, 9:15 a.m. | 24\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nceph: fix memory leak in ceph_direct_read_write()  \n  \nThe bvecs array which is allocated in iter_get_bvecs_alloc() is leaked  \nand pages remain pinned if ceph_alloc_sparse_ext_map() fails.  \n  \nThere is no need to delay the allocation of sparse_ext map until after  \nthe bvecs array is set up, so fix this by moving sparse_ext allocation  \na bit earlier.  Also, make a similar adjustment in __ceph_sync_read()  \nfor consistency (a leak of the same kind in __ceph_sync_read() has been  \naddressed differently). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T10:41:24.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/fb15a5f4-bd14-4c91-9d07-ac260b1824e7/export</guid>
      <pubDate>Sun, 29 Dec 2024 10:41:24 +0000</pubDate>
    </item>
    <item>
      <title>084249b6-6717-4345-976f-25226c72ad3d</title>
      <link>https://vulnerability.circl.lu/sighting/084249b6-6717-4345-976f-25226c72ad3d/export</link>
      <description>{"uuid": "084249b6-6717-4345-976f-25226c72ad3d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56717", "type": "seen", "source": "https://t.me/cvedetector/13869", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56717 - \"DNX: Linux Kernel Net: Incorrect SRC_PORT Field In Ocelot Ifh Set Basic\"\", \n  \"Content\": \"CVE ID : CVE-2024-56717 \nPublished : Dec. 29, 2024, 9:15 a.m. | 24\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic()  \n  \nPackets injected by the CPU should have a SRC_PORT field equal to the  \nCPU port module index in the Analyzer block (ocelot-&amp;gt;num_phys_ports).  \n  \nThe blamed commit copied the ocelot_ifh_set_basic() call incorrectly  \nfrom ocelot_xmit_common() in net/dsa/tag_ocelot.c. Instead of calling  \nwith \"x\", it calls with BIT_ULL(x), but the field is not a port mask,  \nbut rather a single port index.  \n  \n[ side note: this is the technical debt of code duplication :( ]  \n  \nThe error used to be silent and doesn't appear to have other  \nuser-visible manifestations, but with new changes in the packing  \nlibrary, it now fails loudly as follows:  \n  \n------------[ cut here ]------------  \nCannot store 0x40 inside bits 46-43 - will truncate  \nsja1105 spi2.0: xmit timed out  \nWARNING: CPU: 1 PID: 102 at lib/packing.c:98 __pack+0x90/0x198  \nsja1105 spi2.0: timed out polling for tstamp  \nCPU: 1 UID: 0 PID: 102 Comm: felix_xmit  \nTainted: G        W        N 6.13.0-rc1-00372-gf706b85d972d-dirty #2605  \nCall trace:  \n __pack+0x90/0x198 (P)  \n __pack+0x90/0x198 (L)  \n packing+0x78/0x98  \n ocelot_ifh_set_basic+0x260/0x368  \n ocelot_port_inject_frame+0xa8/0x250  \n felix_port_deferred_xmit+0x14c/0x258  \n kthread_worker_fn+0x134/0x350  \n kthread+0x114/0x138  \n  \nThe code path pertains to the ocelot switchdev driver and to the felix  \nsecondary DSA tag protocol, ocelot-8021q. Here seen with ocelot-8021q.  \n  \nThe messenger (packing) is not really to blame, so fix the original  \ncommit instead. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T10:41:18.000000Z"}</description>
      <content:encoded>{"uuid": "084249b6-6717-4345-976f-25226c72ad3d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56717", "type": "seen", "source": "https://t.me/cvedetector/13869", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56717 - \"DNX: Linux Kernel Net: Incorrect SRC_PORT Field In Ocelot Ifh Set Basic\"\", \n  \"Content\": \"CVE ID : CVE-2024-56717 \nPublished : Dec. 29, 2024, 9:15 a.m. | 24\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic()  \n  \nPackets injected by the CPU should have a SRC_PORT field equal to the  \nCPU port module index in the Analyzer block (ocelot-&amp;gt;num_phys_ports).  \n  \nThe blamed commit copied the ocelot_ifh_set_basic() call incorrectly  \nfrom ocelot_xmit_common() in net/dsa/tag_ocelot.c. Instead of calling  \nwith \"x\", it calls with BIT_ULL(x), but the field is not a port mask,  \nbut rather a single port index.  \n  \n[ side note: this is the technical debt of code duplication :( ]  \n  \nThe error used to be silent and doesn't appear to have other  \nuser-visible manifestations, but with new changes in the packing  \nlibrary, it now fails loudly as follows:  \n  \n------------[ cut here ]------------  \nCannot store 0x40 inside bits 46-43 - will truncate  \nsja1105 spi2.0: xmit timed out  \nWARNING: CPU: 1 PID: 102 at lib/packing.c:98 __pack+0x90/0x198  \nsja1105 spi2.0: timed out polling for tstamp  \nCPU: 1 UID: 0 PID: 102 Comm: felix_xmit  \nTainted: G        W        N 6.13.0-rc1-00372-gf706b85d972d-dirty #2605  \nCall trace:  \n __pack+0x90/0x198 (P)  \n __pack+0x90/0x198 (L)  \n packing+0x78/0x98  \n ocelot_ifh_set_basic+0x260/0x368  \n ocelot_port_inject_frame+0xa8/0x250  \n felix_port_deferred_xmit+0x14c/0x258  \n kthread_worker_fn+0x134/0x350  \n kthread+0x114/0x138  \n  \nThe code path pertains to the ocelot switchdev driver and to the felix  \nsecondary DSA tag protocol, ocelot-8021q. Here seen with ocelot-8021q.  \n  \nThe messenger (packing) is not really to blame, so fix the original  \ncommit instead. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T10:41:18.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/084249b6-6717-4345-976f-25226c72ad3d/export</guid>
      <pubDate>Sun, 29 Dec 2024 10:41:18 +0000</pubDate>
    </item>
    <item>
      <title>ece09607-504c-4bac-a81e-df946c5c4357</title>
      <link>https://vulnerability.circl.lu/sighting/ece09607-504c-4bac-a81e-df946c5c4357/export</link>
      <description>{"uuid": "ece09607-504c-4bac-a81e-df946c5c4357", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56716", "type": "seen", "source": "https://t.me/cvedetector/13868", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56716 - Netdevsim Kernel Information Disclosure and Crash Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56716 \nPublished : Dec. 29, 2024, 9:15 a.m. | 24\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetdevsim: prevent bad user input in nsim_dev_health_break_write()  \n  \nIf either a zero count or a large one is provided, kernel can crash. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T10:41:17.000000Z"}</description>
      <content:encoded>{"uuid": "ece09607-504c-4bac-a81e-df946c5c4357", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56716", "type": "seen", "source": "https://t.me/cvedetector/13868", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56716 - Netdevsim Kernel Information Disclosure and Crash Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56716 \nPublished : Dec. 29, 2024, 9:15 a.m. | 24\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetdevsim: prevent bad user input in nsim_dev_health_break_write()  \n  \nIf either a zero count or a large one is provided, kernel can crash. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T10:41:17.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/ece09607-504c-4bac-a81e-df946c5c4357/export</guid>
      <pubDate>Sun, 29 Dec 2024 10:41:17 +0000</pubDate>
    </item>
  </channel>
</rss>
