https://db.gcve.eu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Mon, 11 May 2026 04:37:47 +0000 https://db.gcve.eu/sighting/0319e620-3be1-4aa2-93f7-3bc507322f01/export {"uuid": "0319e620-3be1-4aa2-93f7-3bc507322f01", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53083", "type": "seen", "source": "https://t.me/cvedetector/11484", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53083 - Qualcomm USB Type-C PMIC Uninitialized Data Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-53083 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nusb: typec: qcom-pmic: init value of hdr_len/txbuf_len earlier \n \nIf the read of USB_PDPHY_RX_ACKNOWLEDGE_REG failed, then hdr_len and \ntxbuf_len are uninitialized. This commit stops to print uninitialized \nvalue and misleading/false data. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:43.000000Z"} {"uuid": "0319e620-3be1-4aa2-93f7-3bc507322f01", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53083", "type": "seen", "source": "https://t.me/cvedetector/11484", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53083 - Qualcomm USB Type-C PMIC Uninitialized Data Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-53083 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nusb: typec: qcom-pmic: init value of hdr_len/txbuf_len earlier \n \nIf the read of USB_PDPHY_RX_ACKNOWLEDGE_REG failed, then hdr_len and \ntxbuf_len are uninitialized. This commit stops to print uninitialized \nvalue and misleading/false data. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:43.000000Z"} https://db.gcve.eu/sighting/0319e620-3be1-4aa2-93f7-3bc507322f01/export Tue, 19 Nov 2024 20:09:43 +0000 https://db.gcve.eu/sighting/6cd9cc86-480e-4803-bb7a-eda2c61bb971/export {"uuid": "6cd9cc86-480e-4803-bb7a-eda2c61bb971", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53082", "type": "seen", "source": "https://t.me/cvedetector/11485", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53082 - \"VMware ESXi Out-of-Bound Write\"\", \n \"Content\": \"CVE ID : CVE-2024-53082 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nvirtio_net: Add hash_key_length check \n \nAdd hash_key_length check in virtnet_probe() to avoid possible out of \nbound errors when setting/reading the hash key. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:45.000000Z"} {"uuid": "6cd9cc86-480e-4803-bb7a-eda2c61bb971", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53082", "type": "seen", "source": "https://t.me/cvedetector/11485", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53082 - \"VMware ESXi Out-of-Bound Write\"\", \n \"Content\": \"CVE ID : CVE-2024-53082 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nvirtio_net: Add hash_key_length check \n \nAdd hash_key_length check in virtnet_probe() to avoid possible out of \nbound errors when setting/reading the hash key. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:45.000000Z"} https://db.gcve.eu/sighting/6cd9cc86-480e-4803-bb7a-eda2c61bb971/export Tue, 19 Nov 2024 20:09:45 +0000 https://db.gcve.eu/sighting/d5ce88fd-7f46-4abf-9b4b-12e329ab3cf1/export {"uuid": "d5ce88fd-7f46-4abf-9b4b-12e329ab3cf1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53084", "type": "seen", "source": "https://t.me/cvedetector/11486", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53084 - Imagination PVR Linux Kernel Object Reference Leak\", \n \"Content\": \"CVE ID : CVE-2024-53084 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/imagination: Break an object reference loop \n \nWhen remaining resources are being cleaned up on driver close, \noutstanding VM mappings may result in resources being leaked, due \nto an object reference loop, as shown below, with each object (or \nset of objects) referencing the object below it: \n \n PVR GEM Object \n GPU scheduler \"finished\" fence \n GPU scheduler \u201cscheduled\u201d fence \n PVR driver \u201cdone\u201d fence \n PVR Context \n PVR VM Context \n PVR VM Mappings \n PVR GEM Object \n \nThe reference that the PVR VM Context has on the VM mappings is a \nsoft one, in the sense that the freeing of outstanding VM mappings \nis done as part of VM context destruction; no reference counts are \ninvolved, as is the case for all the other references in the loop. \n \nTo break the reference loop during cleanup, free the outstanding \nVM mappings before destroying the PVR Context associated with the \nVM context. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:46.000000Z"} {"uuid": "d5ce88fd-7f46-4abf-9b4b-12e329ab3cf1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53084", "type": "seen", "source": "https://t.me/cvedetector/11486", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53084 - Imagination PVR Linux Kernel Object Reference Leak\", \n \"Content\": \"CVE ID : CVE-2024-53084 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/imagination: Break an object reference loop \n \nWhen remaining resources are being cleaned up on driver close, \noutstanding VM mappings may result in resources being leaked, due \nto an object reference loop, as shown below, with each object (or \nset of objects) referencing the object below it: \n \n PVR GEM Object \n GPU scheduler \"finished\" fence \n GPU scheduler \u201cscheduled\u201d fence \n PVR driver \u201cdone\u201d fence \n PVR Context \n PVR VM Context \n PVR VM Mappings \n PVR GEM Object \n \nThe reference that the PVR VM Context has on the VM mappings is a \nsoft one, in the sense that the freeing of outstanding VM mappings \nis done as part of VM context destruction; no reference counts are \ninvolved, as is the case for all the other references in the loop. \n \nTo break the reference loop during cleanup, free the outstanding \nVM mappings before destroying the PVR Context associated with the \nVM context. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:46.000000Z"} https://db.gcve.eu/sighting/d5ce88fd-7f46-4abf-9b4b-12e329ab3cf1/export Tue, 19 Nov 2024 20:09:46 +0000 https://db.gcve.eu/sighting/afe7e3df-40ee-43e0-a768-263efc3719d3/export {"uuid": "afe7e3df-40ee-43e0-a768-263efc3719d3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53085", "type": "seen", "source": "https://t.me/cvedetector/11487", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53085 - \"Linux Tpm Lock Discipline Info Disclosure\"\", \n \"Content\": \"CVE ID : CVE-2024-53085 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ntpm: Lock TPM chip in tpm_pm_suspend() first \n \nSetting TPM_CHIP_FLAG_SUSPENDED in the end of tpm_pm_suspend() can be racy \naccording, as this leaves window for tpm_hwrng_read() to be called while \nthe operation is in progress. The recent bug report gives also evidence of \nthis behaviour. \n \nAadress this by locking the TPM chip before checking any chip->flags both \nin tpm_pm_suspend() and tpm_hwrng_read(). Move TPM_CHIP_FLAG_SUSPENDED \ncheck inside tpm_get_random() so that it will be always checked only when \nthe lock is reserved. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:47.000000Z"} {"uuid": "afe7e3df-40ee-43e0-a768-263efc3719d3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53085", "type": "seen", "source": "https://t.me/cvedetector/11487", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53085 - \"Linux Tpm Lock Discipline Info Disclosure\"\", \n \"Content\": \"CVE ID : CVE-2024-53085 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ntpm: Lock TPM chip in tpm_pm_suspend() first \n \nSetting TPM_CHIP_FLAG_SUSPENDED in the end of tpm_pm_suspend() can be racy \naccording, as this leaves window for tpm_hwrng_read() to be called while \nthe operation is in progress. The recent bug report gives also evidence of \nthis behaviour. \n \nAadress this by locking the TPM chip before checking any chip->flags both \nin tpm_pm_suspend() and tpm_hwrng_read(). Move TPM_CHIP_FLAG_SUSPENDED \ncheck inside tpm_get_random() so that it will be always checked only when \nthe lock is reserved. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:47.000000Z"} https://db.gcve.eu/sighting/afe7e3df-40ee-43e0-a768-263efc3719d3/export Tue, 19 Nov 2024 20:09:47 +0000 https://db.gcve.eu/sighting/e83ec22d-6bb4-449a-a7e2-e4608252cb45/export {"uuid": "e83ec22d-6bb4-449a-a7e2-e4608252cb45", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53086", "type": "seen", "source": "https://t.me/cvedetector/11488", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53086 - Mesa Xorg Driver Memory Leak Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-53086 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/xe: Drop VM dma-resv lock on xe_sync_in_fence_get failure in exec IOCTL \n \nUpon failure all locks need to be dropped before returning to the user. \n \n(cherry picked from commit 7d1a4258e602ffdce529f56686925034c1b3b095) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:48.000000Z"} {"uuid": "e83ec22d-6bb4-449a-a7e2-e4608252cb45", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53086", "type": "seen", "source": "https://t.me/cvedetector/11488", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53086 - Mesa Xorg Driver Memory Leak Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-53086 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/xe: Drop VM dma-resv lock on xe_sync_in_fence_get failure in exec IOCTL \n \nUpon failure all locks need to be dropped before returning to the user. \n \n(cherry picked from commit 7d1a4258e602ffdce529f56686925034c1b3b095) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:48.000000Z"} https://db.gcve.eu/sighting/e83ec22d-6bb4-449a-a7e2-e4608252cb45/export Tue, 19 Nov 2024 20:09:48 +0000 https://db.gcve.eu/sighting/9d83daea-06f4-4f59-95f6-7ec68e2c20fb/export {"uuid": "9d83daea-06f4-4f59-95f6-7ec68e2c20fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53088", "type": "seen", "source": "https://t.me/cvedetector/11491", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53088 - Intel i40e Linux Kernel MAC/VLAN Filter Race Condition Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-53088 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ni40e: fix race condition by adding filter's intermediate sync state \n \nFix a race condition in the i40e driver that leads to MAC/VLAN filters \nbecoming corrupted and leaking. Address the issue that occurs under \nheavy load when multiple threads are concurrently modifying MAC/VLAN \nfilters by setting mac and port VLAN. \n \n1. Thread T0 allocates a filter in i40e_add_filter() within \n i40e_ndo_set_vf_port_vlan(). \n2. Thread T1 concurrently frees the filter in __i40e_del_filter() within \n i40e_ndo_set_vf_mac(). \n3. Subsequently, i40e_service_task() calls i40e_sync_vsi_filters(), which \n refers to the already freed filter memory, causing corruption. \n \nReproduction steps: \n1. Spawn multiple VFs. \n2. Apply a concurrent heavy load by running parallel operations to change \n MAC addresses on the VFs and change port VLANs on the host. \n3. Observe errors in dmesg: \n\"Error I40E_AQ_RC_ENOSPC adding RX filters on VF XX, \n please set promiscuous on manually for VF XX\". \n \nExact code for stable reproduction Intel can't open-source now. \n \nThe fix involves implementing a new intermediate filter state, \nI40E_FILTER_NEW_SYNC, for the time when a filter is on a tmp_add_list. \nThese filters cannot be deleted from the hash list directly but \nmust be removed using the full process. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:52.000000Z"} {"uuid": "9d83daea-06f4-4f59-95f6-7ec68e2c20fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53088", "type": "seen", "source": "https://t.me/cvedetector/11491", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53088 - Intel i40e Linux Kernel MAC/VLAN Filter Race Condition Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-53088 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ni40e: fix race condition by adding filter's intermediate sync state \n \nFix a race condition in the i40e driver that leads to MAC/VLAN filters \nbecoming corrupted and leaking. Address the issue that occurs under \nheavy load when multiple threads are concurrently modifying MAC/VLAN \nfilters by setting mac and port VLAN. \n \n1. Thread T0 allocates a filter in i40e_add_filter() within \n i40e_ndo_set_vf_port_vlan(). \n2. Thread T1 concurrently frees the filter in __i40e_del_filter() within \n i40e_ndo_set_vf_mac(). \n3. Subsequently, i40e_service_task() calls i40e_sync_vsi_filters(), which \n refers to the already freed filter memory, causing corruption. \n \nReproduction steps: \n1. Spawn multiple VFs. \n2. Apply a concurrent heavy load by running parallel operations to change \n MAC addresses on the VFs and change port VLANs on the host. \n3. Observe errors in dmesg: \n\"Error I40E_AQ_RC_ENOSPC adding RX filters on VF XX, \n please set promiscuous on manually for VF XX\". \n \nExact code for stable reproduction Intel can't open-source now. \n \nThe fix involves implementing a new intermediate filter state, \nI40E_FILTER_NEW_SYNC, for the time when a filter is on a tmp_add_list. \nThese filters cannot be deleted from the hash list directly but \nmust be removed using the full process. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:52.000000Z"} https://db.gcve.eu/sighting/9d83daea-06f4-4f59-95f6-7ec68e2c20fb/export Tue, 19 Nov 2024 20:09:52 +0000 https://db.gcve.eu/sighting/1329156f-c236-4251-a8a0-b631ae6bb335/export {"uuid": "1329156f-c236-4251-a8a0-b631ae6bb335", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53089", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113522350666278437", "content": "", "creation_timestamp": "2024-11-21T18:26:43.632705Z"} {"uuid": "1329156f-c236-4251-a8a0-b631ae6bb335", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53089", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113522350666278437", "content": "", "creation_timestamp": "2024-11-21T18:26:43.632705Z"} https://db.gcve.eu/sighting/1329156f-c236-4251-a8a0-b631ae6bb335/export Thu, 21 Nov 2024 18:26:43 +0000 https://db.gcve.eu/sighting/b5484c4b-6a21-45e0-a5c8-2c1e560bb024/export {"uuid": "b5484c4b-6a21-45e0-a5c8-2c1e560bb024", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-5308", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhultuptdq2x", "content": "", "creation_timestamp": "2025-02-11T02:19:17.821333Z"} {"uuid": "b5484c4b-6a21-45e0-a5c8-2c1e560bb024", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-5308", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhultuptdq2x", "content": "", "creation_timestamp": "2025-02-11T02:19:17.821333Z"} https://db.gcve.eu/sighting/b5484c4b-6a21-45e0-a5c8-2c1e560bb024/export Tue, 11 Feb 2025 02:19:17 +0000 https://db.gcve.eu/sighting/c08921bc-c3d2-40fe-aeb2-3b6b8aabac07/export {"uuid": "c08921bc-c3d2-40fe-aeb2-3b6b8aabac07", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53088", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "c08921bc-c3d2-40fe-aeb2-3b6b8aabac07", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53088", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} https://db.gcve.eu/sighting/c08921bc-c3d2-40fe-aeb2-3b6b8aabac07/export Wed, 03 Dec 2025 14:14:49 +0000 https://db.gcve.eu/sighting/24fed17b-263a-4cec-97bb-d8b21d4c2b65/export {"uuid": "24fed17b-263a-4cec-97bb-d8b21d4c2b65", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53089", "type": "seen", "source": "https://bsky.app/profile/secqube.com/post/3m7oxcps3hx2s", "content": "", "creation_timestamp": "2025-12-11T06:33:08.504932Z"} {"uuid": "24fed17b-263a-4cec-97bb-d8b21d4c2b65", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53089", "type": "seen", "source": "https://bsky.app/profile/secqube.com/post/3m7oxcps3hx2s", "content": "", "creation_timestamp": "2025-12-11T06:33:08.504932Z"} https://db.gcve.eu/sighting/24fed17b-263a-4cec-97bb-d8b21d4c2b65/export Thu, 11 Dec 2025 06:33:08 +0000