{"vulnerability": "CVE-2024-4107", "sightings": [{"uuid": "592b1fda-3935-45db-a084-dac7520447d7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-41074", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "57f06fec-6112-40ad-89b1-e4631873443a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41078", "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": "362ba028-05e7-456e-86c2-96433ed639dc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41070", "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": "b7cdcee4-16ba-44d5-a5b9-e503701d81eb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41072", "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": "c1ce59c3-2ca4-4a4f-8233-2682432f2ac8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41077", "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": "8094eb21-ab33-4f89-ad0e-66e80b7c3b94", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-41075", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "a49d53d3-0b0a-454b-9f4b-e398af68f7a8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-41079", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "4a4c921c-d9e1-438c-9991-b956c64ef8bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-41079", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "29133670-5c76-463d-9e84-5ced460bb0ff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-41077", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "010c2e65-49b7-413f-8a8c-67a1fba69f12", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-41076", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "514d0b91-89c6-444e-9c3b-ef9ba928ec65", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-41078", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "c0323f7f-8826-4fb6-aaa6-2d42c1710e8b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-41073", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "c0ac0c2e-680c-404f-9be0-4a3fd1e2419a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41077", "type": "seen", "source": "https://t.me/cvedetector/1854", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41077 - Linux Kernel null_blk Power of 2 Block Size Validation Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-41077 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnull_blk: fix validation of block size  \n  \nBlock size should be between 512 and PAGE_SIZE and be a power of 2. The current  \ncheck does not validate this, so update the check.  \n  \nWithout this patch, null_blk would Oops due to a null pointer deref when  \nloaded with bs=1536 [1].  \n  \n  \n[axboe: remove unnecessary braces and != 0 check] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:57:55.000000Z"}, {"uuid": "88e6fc25-4c72-4acd-b82e-e896e7dc20cf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41072", "type": "seen", "source": "https://t.me/cvedetector/1870", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41072 - \"WiFi Linux Kernel Invalid Channels Check Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-41072 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: cfg80211: wext: add extra SIOCSIWSCAN data check  \n  \nIn 'cfg80211_wext_siwscan()', add extra check whether number of  \nchannels passed via 'ioctl(sock, SIOCSIWSCAN, ...)' doesn't exceed  \nIW_MAX_FREQUENCIES and reject invalid request with -EINVAL otherwise. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:58:15.000000Z"}, {"uuid": "5e4fae45-3563-4bbb-922d-eefcc39b4ee0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41070", "type": "seen", "source": "https://t.me/cvedetector/1869", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41070 - KVM powerpc PPCHV Use-After-Free\", \n  \"Content\": \"CVE ID : CVE-2024-41070 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nKVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group()  \n  \nAl reported a possible use-after-free (UAF) in kvm_spapr_tce_attach_iommu_group().  \n  \nIt looks up `stt` from tablefd, but then continues to use it after doing  \nfdput() on the returned fd. After the fdput() the tablefd is free to be  \nclosed by another thread. The close calls kvm_spapr_tce_release() and  \nthen release_spapr_tce_table() (via call_rcu()) which frees `stt`.  \n  \nAlthough there are calls to rcu_read_lock() in  \nkvm_spapr_tce_attach_iommu_group() they are not sufficient to prevent  \nthe UAF, because `stt` is used outside the locked regions.  \n  \nWith an artifcial delay after the fdput() and a userspace program which  \ntriggers the race, KASAN detects the UAF:  \n  \n  BUG: KASAN: slab-use-after-free in kvm_spapr_tce_attach_iommu_group+0x298/0x720 [kvm]  \n  Read of size 4 at addr c000200027552c30 by task kvm-vfio/2505  \n  CPU: 54 PID: 2505 Comm: kvm-vfio Not tainted 6.10.0-rc3-next-20240612-dirty #1  \n  Hardware name: 8335-GTH POWER9 0x4e1202 opal:skiboot-v6.5.3-35-g1851b2a06 PowerNV  \n  Call Trace:  \n    dump_stack_lvl+0xb4/0x108 (unreliable)  \n    print_report+0x2b4/0x6ec  \n    kasan_report+0x118/0x2b0  \n    __asan_load4+0xb8/0xd0  \n    kvm_spapr_tce_attach_iommu_group+0x298/0x720 [kvm]  \n    kvm_vfio_set_attr+0x524/0xac0 [kvm]  \n    kvm_device_ioctl+0x144/0x240 [kvm]  \n    sys_ioctl+0x62c/0x1810  \n    system_call_exception+0x190/0x440  \n    system_call_vectored_common+0x15c/0x2ec  \n  ...  \n  Freed by task 0:  \n   ...  \n   kfree+0xec/0x3e0  \n   release_spapr_tce_table+0xd4/0x11c [kvm]  \n   rcu_core+0x568/0x16a0  \n   handle_softirqs+0x23c/0x920  \n   do_softirq_own_stack+0x6c/0x90  \n   do_softirq_own_stack+0x58/0x90  \n   __irq_exit_rcu+0x218/0x2d0  \n   irq_exit+0x30/0x80  \n   arch_local_irq_restore+0x128/0x230  \n   arch_local_irq_enable+0x1c/0x30  \n   cpuidle_enter_state+0x134/0x5cc  \n   cpuidle_enter+0x6c/0xb0  \n   call_cpuidle+0x7c/0x100  \n   do_idle+0x394/0x410  \n   cpu_startup_entry+0x60/0x70  \n   start_secondary+0x3fc/0x410  \n   start_secondary_prolog+0x10/0x14  \n  \nFix it by delaying the fdput() until `stt` is no longer in use, which  \nis effectively the entire function. To keep the patch minimal add a call  \nto fdput() at each of the existing return paths. Future work can convert  \nthe function to goto or __cleanup style cleanup.  \n  \nWith the fix in place the test case no longer triggers the UAF. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:58:14.000000Z"}, {"uuid": "679cc19d-8b13-4f74-977b-c8af9f9ed0fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41071", "type": "seen", "source": "https://t.me/cvedetector/1867", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41071 - Linux Wireless MAC80211 Array Index Out of Bounds Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-41071 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: mac80211: Avoid address calculations via out of bounds array indexing  \n  \nreq->n_channels must be set before req->channels[] can be used.  \n  \nThis patch fixes one of the issues encountered in [1].  \n  \n[   83.964255] UBSAN: array-index-out-of-bounds in net/mac80211/scan.c:364:4  \n[   83.964258] index 0 is out of range for type 'struct ieee80211_channel *[]'  \n[...]  \n[   83.964264] Call Trace:  \n[   83.964267]    \n[   83.964269]  dump_stack_lvl+0x3f/0xc0  \n[   83.964274]  __ubsan_handle_out_of_bounds+0xec/0x110  \n[   83.964278]  ieee80211_prep_hw_scan+0x2db/0x4b0  \n[   83.964281]  __ieee80211_start_scan+0x601/0x990  \n[   83.964291]  nl80211_trigger_scan+0x874/0x980  \n[   83.964295]  genl_family_rcv_msg_doit+0xe8/0x160  \n[   83.964298]  genl_rcv_msg+0x240/0x270  \n[...]  \n  \n[1]  \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:58:12.000000Z"}, {"uuid": "cf49e12a-a02d-4418-b04c-f65bf06a18e3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41073", "type": "seen", "source": "https://t.me/cvedetector/1864", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41073 - NVIDIA NVMe Double Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-41073 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnvme: avoid double free special payload  \n  \nIf a discard request needs to be retried, and that retry may fail before  \na new special payload is added, a double free will result. Clear the  \nRQF_SPECIAL_LOAD when the request is cleaned. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:58:09.000000Z"}, {"uuid": "225366ad-e3d3-4169-a28c-3735899eaa59", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41074", "type": "seen", "source": "https://t.me/cvedetector/1863", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41074 - Linux Kernel Cachefiles Request Deletion.VisibleIndex Desync\", \n  \"Content\": \"CVE ID : CVE-2024-41074 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncachefiles: Set object to close if ondemand_id Severity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:58:08.000000Z"}, {"uuid": "d496aeb8-f16e-47a9-999c-0bbb2428d7c8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41076", "type": "seen", "source": "https://t.me/cvedetector/1861", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41076 - \"Linux Kernel NFSv4 Memory Leak Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-41076 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nNFSv4: Fix memory leak in nfs4_set_security_label  \n  \nWe leak nfs_fattr and nfs4_label every time we set a security xattr. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:58:06.000000Z"}, {"uuid": "77c579ba-f6c4-46bd-8d23-740e715b2ad5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41078", "type": "seen", "source": "https://t.me/cvedetector/1859", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41078 - Btrfs Quota Root Leak\", \n  \"Content\": \"CVE ID : CVE-2024-41078 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbtrfs: qgroup: fix quota root leak after quota disable failure  \n  \nIf during the quota disable we fail when cleaning the quota tree or when  \ndeleting the root from the root tree, we jump to the 'out' label without  \never dropping the reference on the quota root, resulting in a leak of the  \nroot since fs_info->quota_root is no longer pointing to the root (we have  \nset it to NULL just before those steps).  \n  \nFix this by always doing a btrfs_put_root() call under the 'out' label.  \nThis is a problem that exists since qgroups were first added in 2012 by  \ncommit bed92eae26cc (\"Btrfs: qgroup implementation and prototypes\"), but  \nback then we missed a kfree on the quota root and free_extent_buffer()  \ncalls on its root and commit root nodes, since back then roots were not  \nyet reference counted. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:58:04.000000Z"}, {"uuid": "726d1cb6-a044-4d78-9683-4fe2ea762fba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41075", "type": "seen", "source": "https://t.me/cvedetector/1856", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41075 - Linux Kernel cachefiles Denial of Service (DoS) and Crash Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-41075 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncachefiles: add consistency check for copen/cread  \n  \nThis prevents malicious processes from completing random copen/cread  \nrequests and crashing the system. Added checks are listed below:  \n  \n  * Generic, copen can only complete open requests, and cread can only  \n    complete read requests.  \n  * For copen, ondemand_id must not be 0, because this indicates that the  \n    request has not been read by the daemon.  \n  * For cread, the object corresponding to fd and req should be the same. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:57:57.000000Z"}, {"uuid": "7b29a9ba-e376-424e-ad68-4a2e0590af1b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41079", "type": "seen", "source": "https://t.me/cvedetector/1855", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41079 - NVIDIA NVMe Target Memory Disclosure\", \n  \"Content\": \"CVE ID : CVE-2024-41079 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnvmet: always initialize cqe.result  \n  \nThe spec doesn't mandate that the first two double words (aka results)  \nfor the command queue entry need to be set to 0 when they are not  \nused (not specified). Though, the target implemention returns 0 for TCP  \nand FC but not for RDMA.  \n  \nLet's make RDMA behave the same and thus explicitly initializing the  \nresult field. This prevents leaking any data from the stack. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:57:56.000000Z"}, {"uuid": "e61eeff9-da6b-4c49-b7a9-71f769047d17", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41073", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mlbgryvtcx2q", "content": "\ud83d\udd17 CVE : CVE-2024-41073, CVE-2024-53216, CVE-2025-37861, CVE-2025-40252, CVE-2025-68724, CVE-2025-68741, CVE-2025-71238, CVE-2026-23097, CVE-2026-23136, CVE-2026-23191, CVE-2026-23193, CVE-2026-23243, CVE-2026-23270, CVE-2026-23401, CVE-2026-31402, CVE-2026-31419, CVE-2026-31431, CVE-2026-31532", "creation_timestamp": "2026-05-07T14:35:10.017352Z"}]}