https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Wed, 06 May 2026 05:27:48 +0000 https://vulnerability.circl.lu/sighting/1b82cada-ef60-4567-922c-54d79d7fb9f0/export {"uuid": "1b82cada-ef60-4567-922c-54d79d7fb9f0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50095", "type": "seen", "source": "https://t.me/cvedetector/9907", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50095 - Dell PowerEdge R740 RDMA MAD Agent Soft Lockup Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-50095 \nPublished : Nov. 5, 2024, 5:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nRDMA/mad: Improve handling of timed out WRs of mad agent \n \nCurrent timeout handler of mad agent acquires/releases mad_agent_priv \nlock for every timed out WRs. This causes heavy locking contention \nwhen higher no. of WRs are to be handled inside timeout handler. \n \nThis leads to softlockup with below trace in some use cases where \nrdma-cm path is used to establish connection between peer nodes \n \nTrace: \n----- \n BUG: soft lockup - CPU#4 stuck for 26s! [kworker/u128:3:19767] \n CPU: 4 PID: 19767 Comm: kworker/u128:3 Kdump: loaded Tainted: G OE \n ------- --- 5.14.0-427.13.1.el9_4.x86_64 #1 \n Hardware name: Dell Inc. PowerEdge R740/01YM03, BIOS 2.4.8 11/26/2019 \n Workqueue: ib_mad1 timeout_sends [ib_core] \n RIP: 0010:__do_softirq+0x78/0x2ac \n RSP: 0018:ffffb253449e4f98 EFLAGS: 00000246 \n RAX: 00000000ffffffff RBX: 0000000000000000 RCX: 000000000000001f \n RDX: 000000000000001d RSI: 000000003d1879ab RDI: fff363b66fd3a86b \n RBP: ffffb253604cbcd8 R08: 0000009065635f3b R09: 0000000000000000 \n R10: 0000000000000040 R11: ffffb253449e4ff8 R12: 0000000000000000 \n R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000040 \n FS: 0000000000000000(0000) GS:ffff8caa1fc80000(0000) knlGS:0000000000000000 \n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \n CR2: 00007fd9ec9db900 CR3: 0000000891934006 CR4: 00000000007706e0 \n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 \n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 \n PKRU: 55555554 \n Call Trace: \n \n ? show_trace_log_lvl+0x1c4/0x2df \n ? show_trace_log_lvl+0x1c4/0x2df \n ? __irq_exit_rcu+0xa1/0xc0 \n ? watchdog_timer_fn+0x1b2/0x210 \n ? __pfx_watchdog_timer_fn+0x10/0x10 \n ? __hrtimer_run_queues+0x127/0x2c0 \n ? hrtimer_interrupt+0xfc/0x210 \n ? __sysvec_apic_timer_interrupt+0x5c/0x110 \n ? sysvec_apic_timer_interrupt+0x37/0x90 \n ? asm_sysvec_apic_timer_interrupt+0x16/0x20 \n ? __do_softirq+0x78/0x2ac \n ? __do_softirq+0x60/0x2ac \n __irq_exit_rcu+0xa1/0xc0 \n sysvec_call_function_single+0x72/0x90 \n \n \n asm_sysvec_call_function_single+0x16/0x20 \n RIP: 0010:_raw_spin_unlock_irq+0x14/0x30 \n RSP: 0018:ffffb253604cbd88 EFLAGS: 00000247 \n RAX: 000000000001960d RBX: 0000000000000002 RCX: ffff8cad2a064800 \n RDX: 000000008020001b RSI: 0000000000000001 RDI: ffff8cad5d39f66c \n RBP: ffff8cad5d39f600 R08: 0000000000000001 R09: 0000000000000000 \n R10: ffff8caa443e0c00 R11: ffffb253604cbcd8 R12: ffff8cacb8682538 \n R13: 0000000000000005 R14: ffffb253604cbd90 R15: ffff8cad5d39f66c \n cm_process_send_error+0x122/0x1d0 [ib_cm] \n timeout_sends+0x1dd/0x270 [ib_core] \n process_one_work+0x1e2/0x3b0 \n ? __pfx_worker_thread+0x10/0x10 \n worker_thread+0x50/0x3a0 \n ? __pfx_worker_thread+0x10/0x10 \n kthread+0xdd/0x100 \n ? __pfx_kthread+0x10/0x10 \n ret_from_fork+0x29/0x50 \n \n \nSimplified timeout handler by creating local list of timed out WRs \nand invoke send handler post creating the list. The new method acquires/ \nreleases lock once to fetch the list and hence helps to reduce locking \ncontetiong when processing higher no. of WRs \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"05 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T18:53:55.000000Z"} {"uuid": "1b82cada-ef60-4567-922c-54d79d7fb9f0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50095", "type": "seen", "source": "https://t.me/cvedetector/9907", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50095 - Dell PowerEdge R740 RDMA MAD Agent Soft Lockup Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-50095 \nPublished : Nov. 5, 2024, 5:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nRDMA/mad: Improve handling of timed out WRs of mad agent \n \nCurrent timeout handler of mad agent acquires/releases mad_agent_priv \nlock for every timed out WRs. This causes heavy locking contention \nwhen higher no. of WRs are to be handled inside timeout handler. \n \nThis leads to softlockup with below trace in some use cases where \nrdma-cm path is used to establish connection between peer nodes \n \nTrace: \n----- \n BUG: soft lockup - CPU#4 stuck for 26s! [kworker/u128:3:19767] \n CPU: 4 PID: 19767 Comm: kworker/u128:3 Kdump: loaded Tainted: G OE \n ------- --- 5.14.0-427.13.1.el9_4.x86_64 #1 \n Hardware name: Dell Inc. PowerEdge R740/01YM03, BIOS 2.4.8 11/26/2019 \n Workqueue: ib_mad1 timeout_sends [ib_core] \n RIP: 0010:__do_softirq+0x78/0x2ac \n RSP: 0018:ffffb253449e4f98 EFLAGS: 00000246 \n RAX: 00000000ffffffff RBX: 0000000000000000 RCX: 000000000000001f \n RDX: 000000000000001d RSI: 000000003d1879ab RDI: fff363b66fd3a86b \n RBP: ffffb253604cbcd8 R08: 0000009065635f3b R09: 0000000000000000 \n R10: 0000000000000040 R11: ffffb253449e4ff8 R12: 0000000000000000 \n R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000040 \n FS: 0000000000000000(0000) GS:ffff8caa1fc80000(0000) knlGS:0000000000000000 \n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \n CR2: 00007fd9ec9db900 CR3: 0000000891934006 CR4: 00000000007706e0 \n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 \n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 \n PKRU: 55555554 \n Call Trace: \n \n ? show_trace_log_lvl+0x1c4/0x2df \n ? show_trace_log_lvl+0x1c4/0x2df \n ? __irq_exit_rcu+0xa1/0xc0 \n ? watchdog_timer_fn+0x1b2/0x210 \n ? __pfx_watchdog_timer_fn+0x10/0x10 \n ? __hrtimer_run_queues+0x127/0x2c0 \n ? hrtimer_interrupt+0xfc/0x210 \n ? __sysvec_apic_timer_interrupt+0x5c/0x110 \n ? sysvec_apic_timer_interrupt+0x37/0x90 \n ? asm_sysvec_apic_timer_interrupt+0x16/0x20 \n ? __do_softirq+0x78/0x2ac \n ? __do_softirq+0x60/0x2ac \n __irq_exit_rcu+0xa1/0xc0 \n sysvec_call_function_single+0x72/0x90 \n \n \n asm_sysvec_call_function_single+0x16/0x20 \n RIP: 0010:_raw_spin_unlock_irq+0x14/0x30 \n RSP: 0018:ffffb253604cbd88 EFLAGS: 00000247 \n RAX: 000000000001960d RBX: 0000000000000002 RCX: ffff8cad2a064800 \n RDX: 000000008020001b RSI: 0000000000000001 RDI: ffff8cad5d39f66c \n RBP: ffff8cad5d39f600 R08: 0000000000000001 R09: 0000000000000000 \n R10: ffff8caa443e0c00 R11: ffffb253604cbcd8 R12: ffff8cacb8682538 \n R13: 0000000000000005 R14: ffffb253604cbd90 R15: ffff8cad5d39f66c \n cm_process_send_error+0x122/0x1d0 [ib_cm] \n timeout_sends+0x1dd/0x270 [ib_core] \n process_one_work+0x1e2/0x3b0 \n ? __pfx_worker_thread+0x10/0x10 \n worker_thread+0x50/0x3a0 \n ? __pfx_worker_thread+0x10/0x10 \n kthread+0xdd/0x100 \n ? __pfx_kthread+0x10/0x10 \n ret_from_fork+0x29/0x50 \n \n \nSimplified timeout handler by creating local list of timed out WRs \nand invoke send handler post creating the list. The new method acquires/ \nreleases lock once to fetch the list and hence helps to reduce locking \ncontetiong when processing higher no. of WRs \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"05 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T18:53:55.000000Z"} https://vulnerability.circl.lu/sighting/1b82cada-ef60-4567-922c-54d79d7fb9f0/export Tue, 05 Nov 2024 18:53:55 +0000 https://vulnerability.circl.lu/sighting/7f6244f9-7daf-4bb0-8024-6963fa7456cb/export {"uuid": "7f6244f9-7daf-4bb0-8024-6963fa7456cb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50096", "type": "seen", "source": "https://t.me/cvedetector/9908", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50096 - \"Nouveau DMA Memory Zero-Page Disclosure\"\", \n \"Content\": \"CVE ID : CVE-2024-50096 \nPublished : Nov. 5, 2024, 5:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnouveau/dmem: Fix vulnerability in migrate_to_ram upon copy error \n \nThe `nouveau_dmem_copy_one` function ensures that the copy push command is \nsent to the device firmware but does not track whether it was executed \nsuccessfully. \n \nIn the case of a copy error (e.g., firmware or hardware failure), the \ncopy push command will be sent via the firmware channel, and \n`nouveau_dmem_copy_one` will likely report success, leading to the \n`migrate_to_ram` function returning a dirty HIGH_USER page to the user. \n \nThis can result in a security vulnerability, as a HIGH_USER page that may \ncontain sensitive or corrupted data could be returned to the user. \n \nTo prevent this vulnerability, we allocate a zero page. Thus, in case of \nan error, a non-dirty (zero) page will be returned to the user. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"05 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T18:53:59.000000Z"} {"uuid": "7f6244f9-7daf-4bb0-8024-6963fa7456cb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50096", "type": "seen", "source": "https://t.me/cvedetector/9908", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50096 - \"Nouveau DMA Memory Zero-Page Disclosure\"\", \n \"Content\": \"CVE ID : CVE-2024-50096 \nPublished : Nov. 5, 2024, 5:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnouveau/dmem: Fix vulnerability in migrate_to_ram upon copy error \n \nThe `nouveau_dmem_copy_one` function ensures that the copy push command is \nsent to the device firmware but does not track whether it was executed \nsuccessfully. \n \nIn the case of a copy error (e.g., firmware or hardware failure), the \ncopy push command will be sent via the firmware channel, and \n`nouveau_dmem_copy_one` will likely report success, leading to the \n`migrate_to_ram` function returning a dirty HIGH_USER page to the user. \n \nThis can result in a security vulnerability, as a HIGH_USER page that may \ncontain sensitive or corrupted data could be returned to the user. \n \nTo prevent this vulnerability, we allocate a zero page. Thus, in case of \nan error, a non-dirty (zero) page will be returned to the user. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"05 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T18:53:59.000000Z"} https://vulnerability.circl.lu/sighting/7f6244f9-7daf-4bb0-8024-6963fa7456cb/export Tue, 05 Nov 2024 18:53:59 +0000 https://vulnerability.circl.lu/sighting/93fd50fb-7fd9-487e-ae1c-a032455ba084/export {"uuid": "93fd50fb-7fd9-487e-ae1c-a032455ba084", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50097", "type": "seen", "source": "https://t.me/cvedetector/9909", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50097 - Linux Kernel fec PTP Unconditional Saveidges\", \n \"Content\": \"CVE ID : CVE-2024-50097 \nPublished : Nov. 5, 2024, 5:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet: fec: don't save PTP state if PTP is unsupported \n \nSome platforms (such as i.MX25 and i.MX27) do not support PTP, so on \nthese platforms fec_ptp_init() is not called and the related members \nin fep are not initialized. However, fec_ptp_save_state() is called \nunconditionally, which causes the kernel to panic. Therefore, add a \ncondition so that fec_ptp_save_state() is not called if PTP is not \nsupported. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"05 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T18:54:00.000000Z"} {"uuid": "93fd50fb-7fd9-487e-ae1c-a032455ba084", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50097", "type": "seen", "source": "https://t.me/cvedetector/9909", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50097 - Linux Kernel fec PTP Unconditional Saveidges\", \n \"Content\": \"CVE ID : CVE-2024-50097 \nPublished : Nov. 5, 2024, 5:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet: fec: don't save PTP state if PTP is unsupported \n \nSome platforms (such as i.MX25 and i.MX27) do not support PTP, so on \nthese platforms fec_ptp_init() is not called and the related members \nin fep are not initialized. However, fec_ptp_save_state() is called \nunconditionally, which causes the kernel to panic. Therefore, add a \ncondition so that fec_ptp_save_state() is not called if PTP is not \nsupported. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"05 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T18:54:00.000000Z"} https://vulnerability.circl.lu/sighting/93fd50fb-7fd9-487e-ae1c-a032455ba084/export Tue, 05 Nov 2024 18:54:00 +0000 https://vulnerability.circl.lu/sighting/bff7cba1-426b-4a59-9a96-1816860f77fe/export {"uuid": "bff7cba1-426b-4a59-9a96-1816860f77fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50091", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2167", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-50091\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndm vdo: don't refer to dedupe_context after releasing it\n\nClear the dedupe_context pointer in a data_vio whenever ownership of\nthe context is lost, so that vdo can't examine it accidentally.\n\ud83d\udccf Published: 2024-11-05T17:04:55.311Z\n\ud83d\udccf Modified: 2025-01-17T15:56:22.693Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/63ef073084c67878d7a92e15ad055172da3f05a3\n2. https://git.kernel.org/stable/c/0808ebf2f80b962e75741a41ced372a7116f1e26", "creation_timestamp": "2025-01-17T16:57:09.000000Z"} {"uuid": "bff7cba1-426b-4a59-9a96-1816860f77fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50091", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2167", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-50091\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndm vdo: don't refer to dedupe_context after releasing it\n\nClear the dedupe_context pointer in a data_vio whenever ownership of\nthe context is lost, so that vdo can't examine it accidentally.\n\ud83d\udccf Published: 2024-11-05T17:04:55.311Z\n\ud83d\udccf Modified: 2025-01-17T15:56:22.693Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/63ef073084c67878d7a92e15ad055172da3f05a3\n2. https://git.kernel.org/stable/c/0808ebf2f80b962e75741a41ced372a7116f1e26", "creation_timestamp": "2025-01-17T16:57:09.000000Z"} https://vulnerability.circl.lu/sighting/bff7cba1-426b-4a59-9a96-1816860f77fe/export Fri, 17 Jan 2025 16:57:09 +0000 https://vulnerability.circl.lu/sighting/f8d2fe41-e9bb-4f68-a81a-68ad11cd06d0/export {"uuid": "f8d2fe41-e9bb-4f68-a81a-68ad11cd06d0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50099", "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": "f8d2fe41-e9bb-4f68-a81a-68ad11cd06d0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50099", "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/f8d2fe41-e9bb-4f68-a81a-68ad11cd06d0/export Thu, 14 Aug 2025 10:00:00 +0000 https://vulnerability.circl.lu/sighting/8e1adb8b-400a-4c9e-a358-5449709fe4e2/export {"uuid": "8e1adb8b-400a-4c9e-a358-5449709fe4e2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50096", "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": "8e1adb8b-400a-4c9e-a358-5449709fe4e2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50096", "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/8e1adb8b-400a-4c9e-a358-5449709fe4e2/export Thu, 14 Aug 2025 10:00:00 +0000 https://vulnerability.circl.lu/sighting/b01524b6-6485-4beb-806c-a484bf7c770b/export {"uuid": "b01524b6-6485-4beb-806c-a484bf7c770b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50095", "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": "b01524b6-6485-4beb-806c-a484bf7c770b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50095", "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/b01524b6-6485-4beb-806c-a484bf7c770b/export Thu, 14 Aug 2025 10:00:00 +0000 https://vulnerability.circl.lu/sighting/b1c35d9a-ae8f-4791-8665-d1cd9de6b5dc/export {"uuid": "b1c35d9a-ae8f-4791-8665-d1cd9de6b5dc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-50095", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "b1c35d9a-ae8f-4791-8665-d1cd9de6b5dc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-50095", "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/b1c35d9a-ae8f-4791-8665-d1cd9de6b5dc/export Wed, 03 Dec 2025 14:14:49 +0000 https://vulnerability.circl.lu/sighting/4d6e2158-3654-4b0a-a68f-1e20a6627007/export {"uuid": "4d6e2158-3654-4b0a-a68f-1e20a6627007", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50095", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mbynkk7rzk2z", "content": "", "creation_timestamp": "2026-01-09T13:55:34.175243Z"} {"uuid": "4d6e2158-3654-4b0a-a68f-1e20a6627007", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50095", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mbynkk7rzk2z", "content": "", "creation_timestamp": "2026-01-09T13:55:34.175243Z"} https://vulnerability.circl.lu/sighting/4d6e2158-3654-4b0a-a68f-1e20a6627007/export Fri, 09 Jan 2026 13:55:34 +0000 https://vulnerability.circl.lu/sighting/4016aec0-3342-4882-8ccb-4c90c738927f/export {"uuid": "4016aec0-3342-4882-8ccb-4c90c738927f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-50098", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "4016aec0-3342-4882-8ccb-4c90c738927f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-50098", "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/4016aec0-3342-4882-8ccb-4c90c738927f/export Thu, 19 Mar 2026 00:00:00 +0000