https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Wed, 06 May 2026 08:54:59 +0000 https://vulnerability.circl.lu/sighting/def4ca84-2200-434b-95ea-8f977ee108d6/export {"uuid": "def4ca84-2200-434b-95ea-8f977ee108d6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56692", "type": "seen", "source": "https://t.me/cvedetector/13841", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56692 - \"F2FS Linux Kernel F2fs Block Address Corruption Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2024-56692 \nPublished : Dec. 28, 2024, 10:15 a.m. | 45\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nf2fs: fix to do sanity check on node blkaddr in truncate_node() \n \nsyzbot reports a f2fs bug as below: \n \n------------[ cut here ]------------ \nkernel BUG at fs/f2fs/segment.c:2534! \nRIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534 \nCall Trace: \n truncate_node+0x1ae/0x8c0 fs/f2fs/node.c:909 \n f2fs_remove_inode_page+0x5c2/0x870 fs/f2fs/node.c:1288 \n f2fs_evict_inode+0x879/0x15c0 fs/f2fs/inode.c:856 \n evict+0x4e8/0x9b0 fs/inode.c:723 \n f2fs_handle_failed_inode+0x271/0x2e0 fs/f2fs/inode.c:986 \n f2fs_create+0x357/0x530 fs/f2fs/namei.c:394 \n lookup_open fs/namei.c:3595 [inline] \n open_last_lookups fs/namei.c:3694 [inline] \n path_openat+0x1c03/0x3590 fs/namei.c:3930 \n do_filp_open+0x235/0x490 fs/namei.c:3960 \n do_sys_openat2+0x13e/0x1d0 fs/open.c:1415 \n do_sys_open fs/open.c:1430 [inline] \n __do_sys_openat fs/open.c:1446 [inline] \n __se_sys_openat fs/open.c:1441 [inline] \n __x64_sys_openat+0x247/0x2a0 fs/open.c:1441 \n do_syscall_x64 arch/x86/entry/common.c:52 [inline] \n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 \n entry_SYSCALL_64_after_hwframe+0x77/0x7f \nRIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534 \n \nThe root cause is: on a fuzzed image, blkaddr in nat entry may be \ncorrupted, then it will cause system panic when using it in \nf2fs_invalidate_blocks(), to avoid this, let's add sanity check on \nnat blkaddr in truncate_node(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"28 Dec 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-28T12:06:09.000000Z"} {"uuid": "def4ca84-2200-434b-95ea-8f977ee108d6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56692", "type": "seen", "source": "https://t.me/cvedetector/13841", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56692 - \"F2FS Linux Kernel F2fs Block Address Corruption Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2024-56692 \nPublished : Dec. 28, 2024, 10:15 a.m. | 45\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nf2fs: fix to do sanity check on node blkaddr in truncate_node() \n \nsyzbot reports a f2fs bug as below: \n \n------------[ cut here ]------------ \nkernel BUG at fs/f2fs/segment.c:2534! \nRIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534 \nCall Trace: \n truncate_node+0x1ae/0x8c0 fs/f2fs/node.c:909 \n f2fs_remove_inode_page+0x5c2/0x870 fs/f2fs/node.c:1288 \n f2fs_evict_inode+0x879/0x15c0 fs/f2fs/inode.c:856 \n evict+0x4e8/0x9b0 fs/inode.c:723 \n f2fs_handle_failed_inode+0x271/0x2e0 fs/f2fs/inode.c:986 \n f2fs_create+0x357/0x530 fs/f2fs/namei.c:394 \n lookup_open fs/namei.c:3595 [inline] \n open_last_lookups fs/namei.c:3694 [inline] \n path_openat+0x1c03/0x3590 fs/namei.c:3930 \n do_filp_open+0x235/0x490 fs/namei.c:3960 \n do_sys_openat2+0x13e/0x1d0 fs/open.c:1415 \n do_sys_open fs/open.c:1430 [inline] \n __do_sys_openat fs/open.c:1446 [inline] \n __se_sys_openat fs/open.c:1441 [inline] \n __x64_sys_openat+0x247/0x2a0 fs/open.c:1441 \n do_syscall_x64 arch/x86/entry/common.c:52 [inline] \n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 \n entry_SYSCALL_64_after_hwframe+0x77/0x7f \nRIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534 \n \nThe root cause is: on a fuzzed image, blkaddr in nat entry may be \ncorrupted, then it will cause system panic when using it in \nf2fs_invalidate_blocks(), to avoid this, let's add sanity check on \nnat blkaddr in truncate_node(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"28 Dec 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-28T12:06:09.000000Z"} https://vulnerability.circl.lu/sighting/def4ca84-2200-434b-95ea-8f977ee108d6/export Sat, 28 Dec 2024 12:06:09 +0000 https://vulnerability.circl.lu/sighting/d294869f-3622-4f5d-aebc-313d7d0b892a/export {"uuid": "d294869f-3622-4f5d-aebc-313d7d0b892a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56693", "type": "seen", "source": "https://t.me/cvedetector/13842", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56693 - Linux Kernel - Linux brd/fdisk UAF Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-56693 \nPublished : Dec. 28, 2024, 10:15 a.m. | 45\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbrd: defer automatic disk creation until module initialization succeeds \n \nMy colleague Wupeng found the following problems during fault injection: \n \nBUG: unable to handle page fault for address: fffffbfff809d073 \nPGD 6e648067 P4D 123ec8067 PUD 123ec4067 PMD 100e38067 PTE 0 \nOops: Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI \nCPU: 5 UID: 0 PID: 755 Comm: modprobe Not tainted 6.12.0-rc3+ #17 \nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS \n1.16.1-2.fc37 04/01/2014 \nRIP: 0010:__asan_load8+0x4c/0xa0 \n... \nCall Trace: \n \n blkdev_put_whole+0x41/0x70 \n bdev_release+0x1a3/0x250 \n blkdev_release+0x11/0x20 \n __fput+0x1d7/0x4a0 \n task_work_run+0xfc/0x180 \n syscall_exit_to_user_mode+0x1de/0x1f0 \n do_syscall_64+0x6b/0x170 \n entry_SYSCALL_64_after_hwframe+0x76/0x7e \n \nloop_init() is calling loop_add() after __register_blkdev() succeeds and \nis ignoring disk_add() failure from loop_add(), for loop_add() failure \nis not fatal and successfully created disks are already visible to \nbdev_open(). \n \nbrd_init() is currently calling brd_alloc() before __register_blkdev() \nsucceeds and is releasing successfully created disks when brd_init() \nreturns an error. This can cause UAF for the latter two case: \n \ncase 1: \n T1: \nmodprobe brd \n brd_init \n brd_alloc(0) // success \n add_disk \n disk_scan_partitions \n bdev_file_open_by_dev // alloc file \n fput // won't free until back to userspace \n brd_alloc(1) // failed since mem alloc error inject \n // error path for modprobe will release code segment \n // back to userspace \n __fput \n blkdev_release \n bdev_release \n blkdev_put_whole \n bdev->bd_disk->fops->release // fops is freed now, UAF! \n \ncase 2: \n T1: T2: \nmodprobe brd \n brd_init \n brd_alloc(0) // success \n open(/dev/ram0) \n brd_alloc(1) // fail \n // error path for modprobe \n \n close(/dev/ram0) \n ... \n /* UAF! */ \n bdev->bd_disk->fops->release \n \nFix this problem by following what loop_init() does. Besides, \nreintroduce brd_devices_mutex to help serialize modifications to \nbrd_list. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"28 Dec 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-28T12:06:10.000000Z"} {"uuid": "d294869f-3622-4f5d-aebc-313d7d0b892a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56693", "type": "seen", "source": "https://t.me/cvedetector/13842", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56693 - Linux Kernel - Linux brd/fdisk UAF Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-56693 \nPublished : Dec. 28, 2024, 10:15 a.m. | 45\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbrd: defer automatic disk creation until module initialization succeeds \n \nMy colleague Wupeng found the following problems during fault injection: \n \nBUG: unable to handle page fault for address: fffffbfff809d073 \nPGD 6e648067 P4D 123ec8067 PUD 123ec4067 PMD 100e38067 PTE 0 \nOops: Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI \nCPU: 5 UID: 0 PID: 755 Comm: modprobe Not tainted 6.12.0-rc3+ #17 \nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS \n1.16.1-2.fc37 04/01/2014 \nRIP: 0010:__asan_load8+0x4c/0xa0 \n... \nCall Trace: \n \n blkdev_put_whole+0x41/0x70 \n bdev_release+0x1a3/0x250 \n blkdev_release+0x11/0x20 \n __fput+0x1d7/0x4a0 \n task_work_run+0xfc/0x180 \n syscall_exit_to_user_mode+0x1de/0x1f0 \n do_syscall_64+0x6b/0x170 \n entry_SYSCALL_64_after_hwframe+0x76/0x7e \n \nloop_init() is calling loop_add() after __register_blkdev() succeeds and \nis ignoring disk_add() failure from loop_add(), for loop_add() failure \nis not fatal and successfully created disks are already visible to \nbdev_open(). \n \nbrd_init() is currently calling brd_alloc() before __register_blkdev() \nsucceeds and is releasing successfully created disks when brd_init() \nreturns an error. This can cause UAF for the latter two case: \n \ncase 1: \n T1: \nmodprobe brd \n brd_init \n brd_alloc(0) // success \n add_disk \n disk_scan_partitions \n bdev_file_open_by_dev // alloc file \n fput // won't free until back to userspace \n brd_alloc(1) // failed since mem alloc error inject \n // error path for modprobe will release code segment \n // back to userspace \n __fput \n blkdev_release \n bdev_release \n blkdev_put_whole \n bdev->bd_disk->fops->release // fops is freed now, UAF! \n \ncase 2: \n T1: T2: \nmodprobe brd \n brd_init \n brd_alloc(0) // success \n open(/dev/ram0) \n brd_alloc(1) // fail \n // error path for modprobe \n \n close(/dev/ram0) \n ... \n /* UAF! */ \n bdev->bd_disk->fops->release \n \nFix this problem by following what loop_init() does. Besides, \nreintroduce brd_devices_mutex to help serialize modifications to \nbrd_list. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"28 Dec 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-28T12:06:10.000000Z"} https://vulnerability.circl.lu/sighting/d294869f-3622-4f5d-aebc-313d7d0b892a/export Sat, 28 Dec 2024 12:06:10 +0000 https://vulnerability.circl.lu/sighting/0c882f4f-48d5-4539-80b5-ceb784da406a/export {"uuid": "0c882f4f-48d5-4539-80b5-ceb784da406a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56690", "type": "seen", "source": "https://t.me/cvedetector/13844", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56690 - Linux Kernel PCrypt Cryptographic Manipulation Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-56690 \nPublished : Dec. 28, 2024, 10:15 a.m. | 45\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ncrypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY \n \nSince commit 8f4f68e788c3 (\"crypto: pcrypt - Fix hungtask for \nPADATA_RESET\"), the pcrypt encryption and decryption operations return \n-EAGAIN when the CPU goes online or offline. In alg_test(), a WARN is \ngenerated when pcrypt_aead_decrypt() or pcrypt_aead_encrypt() returns \n-EAGAIN, the unnecessary panic will occur when panic_on_warn set 1. \nFix this issue by calling crypto layer directly without parallelization \nin that case. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"28 Dec 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-28T12:06:48.000000Z"} {"uuid": "0c882f4f-48d5-4539-80b5-ceb784da406a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56690", "type": "seen", "source": "https://t.me/cvedetector/13844", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56690 - Linux Kernel PCrypt Cryptographic Manipulation Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-56690 \nPublished : Dec. 28, 2024, 10:15 a.m. | 45\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ncrypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY \n \nSince commit 8f4f68e788c3 (\"crypto: pcrypt - Fix hungtask for \nPADATA_RESET\"), the pcrypt encryption and decryption operations return \n-EAGAIN when the CPU goes online or offline. In alg_test(), a WARN is \ngenerated when pcrypt_aead_decrypt() or pcrypt_aead_encrypt() returns \n-EAGAIN, the unnecessary panic will occur when panic_on_warn set 1. \nFix this issue by calling crypto layer directly without parallelization \nin that case. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"28 Dec 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-28T12:06:48.000000Z"} https://vulnerability.circl.lu/sighting/0c882f4f-48d5-4539-80b5-ceb784da406a/export Sat, 28 Dec 2024 12:06:48 +0000 https://vulnerability.circl.lu/sighting/1e26ea71-bd74-44c6-90ac-c678d68e7897/export {"uuid": "1e26ea71-bd74-44c6-90ac-c678d68e7897", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56695", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113730923594792294", "content": "", "creation_timestamp": "2024-12-28T14:29:33.379196Z"} {"uuid": "1e26ea71-bd74-44c6-90ac-c678d68e7897", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56695", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113730923594792294", "content": "", "creation_timestamp": "2024-12-28T14:29:33.379196Z"} https://vulnerability.circl.lu/sighting/1e26ea71-bd74-44c6-90ac-c678d68e7897/export Sat, 28 Dec 2024 14:29:33 +0000 https://vulnerability.circl.lu/sighting/5a5fb49b-927a-4bfb-949c-2b08d2374155/export {"uuid": "5a5fb49b-927a-4bfb-949c-2b08d2374155", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56698", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"} {"uuid": "5a5fb49b-927a-4bfb-949c-2b08d2374155", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56698", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"} https://vulnerability.circl.lu/sighting/5a5fb49b-927a-4bfb-949c-2b08d2374155/export Thu, 14 Aug 2025 10:00:00 +0000 https://vulnerability.circl.lu/sighting/1a7b0ab2-7ab0-41fd-9a40-9e3cffcf286f/export {"uuid": "1a7b0ab2-7ab0-41fd-9a40-9e3cffcf286f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56690", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"} {"uuid": "1a7b0ab2-7ab0-41fd-9a40-9e3cffcf286f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56690", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"} https://vulnerability.circl.lu/sighting/1a7b0ab2-7ab0-41fd-9a40-9e3cffcf286f/export Thu, 14 Aug 2025 10:00:00 +0000 https://vulnerability.circl.lu/sighting/4676f373-0bea-4f04-b758-7606d155a766/export {"uuid": "4676f373-0bea-4f04-b758-7606d155a766", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56691", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"} {"uuid": "4676f373-0bea-4f04-b758-7606d155a766", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56691", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"} https://vulnerability.circl.lu/sighting/4676f373-0bea-4f04-b758-7606d155a766/export Thu, 14 Aug 2025 10:00:00 +0000 https://vulnerability.circl.lu/sighting/c3869a6f-1d80-4779-84c3-329b348fb5c9/export {"uuid": "c3869a6f-1d80-4779-84c3-329b348fb5c9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56698", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "c3869a6f-1d80-4779-84c3-329b348fb5c9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56698", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} https://vulnerability.circl.lu/sighting/c3869a6f-1d80-4779-84c3-329b348fb5c9/export Wed, 03 Dec 2025 14:14:49 +0000 https://vulnerability.circl.lu/sighting/c2efc7c8-09c0-4556-b245-327c83139772/export {"uuid": "c2efc7c8-09c0-4556-b245-327c83139772", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56692", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "c2efc7c8-09c0-4556-b245-327c83139772", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56692", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} https://vulnerability.circl.lu/sighting/c2efc7c8-09c0-4556-b245-327c83139772/export Wed, 03 Dec 2025 14:14:49 +0000 https://vulnerability.circl.lu/sighting/be7ec565-45df-4ed0-ba4b-64bd61a0232c/export {"uuid": "be7ec565-45df-4ed0-ba4b-64bd61a0232c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56692", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "be7ec565-45df-4ed0-ba4b-64bd61a0232c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56692", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} https://vulnerability.circl.lu/sighting/be7ec565-45df-4ed0-ba4b-64bd61a0232c/export Thu, 19 Mar 2026 00:00:00 +0000