https://db.gcve.eu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 04 Jun 2026 18:38:13 +0000 https://db.gcve.eu/sighting/76f942d3-8635-480c-a809-856f758d945f/export {"uuid": "76f942d3-8635-480c-a809-856f758d945f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46863", "type": "seen", "source": "https://t.me/cvedetector/6520", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46863 - Intel ASoC Soc-ACPI-lnl-Empty-Item-Class Lack\", \n \"Content\": \"CVE ID : CVE-2024-46863 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nASoC: Intel: soc-acpi-intel-lnl-match: add missing empty item \n \nThere is no links_num in struct snd_soc_acpi_mach {}, and we test \n!link->num_adr as a condition to end the loop in hda_sdw_machine_select(). \nSo an empty item in struct snd_soc_acpi_link_adr array is required. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:26.000000Z"} {"uuid": "76f942d3-8635-480c-a809-856f758d945f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46863", "type": "seen", "source": "https://t.me/cvedetector/6520", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46863 - Intel ASoC Soc-ACPI-lnl-Empty-Item-Class Lack\", \n \"Content\": \"CVE ID : CVE-2024-46863 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nASoC: Intel: soc-acpi-intel-lnl-match: add missing empty item \n \nThere is no links_num in struct snd_soc_acpi_mach {}, and we test \n!link->num_adr as a condition to end the loop in hda_sdw_machine_select(). \nSo an empty item in struct snd_soc_acpi_link_adr array is required. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:26.000000Z"} https://db.gcve.eu/sighting/76f942d3-8635-480c-a809-856f758d945f/export Fri, 27 Sep 2024 15:53:26 +0000 https://db.gcve.eu/sighting/91728044-e050-4130-bebd-748ba64e6d8e/export {"uuid": "91728044-e050-4130-bebd-748ba64e6d8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46864", "type": "seen", "source": "https://t.me/cvedetector/6521", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46864 - Windows Hyper-V Hypervisor Kexec Crash Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-46864 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nx86/hyperv: fix kexec crash due to VP assist page corruption \n \ncommit 9636be85cc5b (\"x86/hyperv: Fix hyperv_pcpu_input_arg handling when \nCPUs go online/offline\") introduces a new cpuhp state for hyperv \ninitialization. \n \ncpuhp_setup_state() returns the state number if state is \nCPUHP_AP_ONLINE_DYN or CPUHP_BP_PREPARE_DYN and 0 for all other states. \nFor the hyperv case, since a new cpuhp state was introduced it would \nreturn 0. However, in hv_machine_shutdown(), the cpuhp_remove_state() call \nis conditioned upon \"hyperv_init_cpuhp > 0\". This will never be true and \nso hv_cpu_die() won't be called on all CPUs. This means the VP assist page \nwon't be reset. When the kexec kernel tries to setup the VP assist page \nagain, the hypervisor corrupts the memory region of the old VP assist page \ncausing a panic in case the kexec kernel is using that memory elsewhere. \nThis was originally fixed in commit dfe94d4086e4 (\"x86/hyperv: Fix kexec \npanic/hang issues\"). \n \nGet rid of hyperv_init_cpuhp entirely since we are no longer using a \ndynamic cpuhp state and use CPUHP_AP_HYPERV_ONLINE directly with \ncpuhp_remove_state(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:27.000000Z"} {"uuid": "91728044-e050-4130-bebd-748ba64e6d8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46864", "type": "seen", "source": "https://t.me/cvedetector/6521", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46864 - Windows Hyper-V Hypervisor Kexec Crash Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-46864 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nx86/hyperv: fix kexec crash due to VP assist page corruption \n \ncommit 9636be85cc5b (\"x86/hyperv: Fix hyperv_pcpu_input_arg handling when \nCPUs go online/offline\") introduces a new cpuhp state for hyperv \ninitialization. \n \ncpuhp_setup_state() returns the state number if state is \nCPUHP_AP_ONLINE_DYN or CPUHP_BP_PREPARE_DYN and 0 for all other states. \nFor the hyperv case, since a new cpuhp state was introduced it would \nreturn 0. However, in hv_machine_shutdown(), the cpuhp_remove_state() call \nis conditioned upon \"hyperv_init_cpuhp > 0\". This will never be true and \nso hv_cpu_die() won't be called on all CPUs. This means the VP assist page \nwon't be reset. When the kexec kernel tries to setup the VP assist page \nagain, the hypervisor corrupts the memory region of the old VP assist page \ncausing a panic in case the kexec kernel is using that memory elsewhere. \nThis was originally fixed in commit dfe94d4086e4 (\"x86/hyperv: Fix kexec \npanic/hang issues\"). \n \nGet rid of hyperv_init_cpuhp entirely since we are no longer using a \ndynamic cpuhp state and use CPUHP_AP_HYPERV_ONLINE directly with \ncpuhp_remove_state(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:27.000000Z"} https://db.gcve.eu/sighting/91728044-e050-4130-bebd-748ba64e6d8e/export Fri, 27 Sep 2024 15:53:27 +0000 https://db.gcve.eu/sighting/001963ca-d820-4fc3-9c43-eb54f02c423e/export {"uuid": "001963ca-d820-4fc3-9c43-eb54f02c423e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46865", "type": "seen", "source": "https://t.me/cvedetector/6522", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46865 - Linux Kernel Fou Null Pointer Dereference\", \n \"Content\": \"CVE ID : CVE-2024-46865 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nfou: fix initialization of grc \n \nThe grc must be initialize first. There can be a condition where if \nfou is NULL, goto out will be executed and grc would be used \nuninitialized. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:28.000000Z"} {"uuid": "001963ca-d820-4fc3-9c43-eb54f02c423e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46865", "type": "seen", "source": "https://t.me/cvedetector/6522", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46865 - Linux Kernel Fou Null Pointer Dereference\", \n \"Content\": \"CVE ID : CVE-2024-46865 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nfou: fix initialization of grc \n \nThe grc must be initialize first. There can be a condition where if \nfou is NULL, goto out will be executed and grc would be used \nuninitialized. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:28.000000Z"} https://db.gcve.eu/sighting/001963ca-d820-4fc3-9c43-eb54f02c423e/export Fri, 27 Sep 2024 15:53:28 +0000 https://db.gcve.eu/sighting/83b74e83-7c91-4b55-97fb-29fcfeed5434/export {"uuid": "83b74e83-7c91-4b55-97fb-29fcfeed5434", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46866", "type": "seen", "source": "https://t.me/cvedetector/6523", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46866 - \"AMD drm Linux Kernel Phabricated Prioritized Confusion\"\", \n \"Content\": \"CVE ID : CVE-2024-46866 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/xe/client: add missing bo locking in show_meminfo() \n \nbo_meminfo() wants to inspect bo state like tt and the ttm resource, \nhowever this state can change at any point leading to stuff like NPD and \nUAF, if the bo lock is not held. Grab the bo lock when calling \nbo_meminfo(), ensuring we drop any spinlocks first. In the case of \nobject_idr we now also need to hold a ref. \n \nv2 (MattB) \n - Also add xe_bo_assert_held() \n \n(cherry picked from commit 4f63d712fa104c3ebefcb289d1e733e86d8698c7) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:29.000000Z"} {"uuid": "83b74e83-7c91-4b55-97fb-29fcfeed5434", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46866", "type": "seen", "source": "https://t.me/cvedetector/6523", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46866 - \"AMD drm Linux Kernel Phabricated Prioritized Confusion\"\", \n \"Content\": \"CVE ID : CVE-2024-46866 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/xe/client: add missing bo locking in show_meminfo() \n \nbo_meminfo() wants to inspect bo state like tt and the ttm resource, \nhowever this state can change at any point leading to stuff like NPD and \nUAF, if the bo lock is not held. Grab the bo lock when calling \nbo_meminfo(), ensuring we drop any spinlocks first. In the case of \nobject_idr we now also need to hold a ref. \n \nv2 (MattB) \n - Also add xe_bo_assert_held() \n \n(cherry picked from commit 4f63d712fa104c3ebefcb289d1e733e86d8698c7) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:29.000000Z"} https://db.gcve.eu/sighting/83b74e83-7c91-4b55-97fb-29fcfeed5434/export Fri, 27 Sep 2024 15:53:29 +0000 https://db.gcve.eu/sighting/f0f6f5bf-5c28-4283-8f8b-ae7eba05d743/export {"uuid": "f0f6f5bf-5c28-4283-8f8b-ae7eba05d743", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46867", "type": "seen", "source": "https://t.me/cvedetector/6524", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46867 - Linux Kernel X.Org drm Atomic Sleeping Lock Deadlock\", \n \"Content\": \"CVE ID : CVE-2024-46867 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/xe/client: fix deadlock in show_meminfo() \n \nThere is a real deadlock as well as sleeping in atomic() bug in here, if \nthe bo put happens to be the last ref, since bo destruction wants to \ngrab the same spinlock and sleeping locks. Fix that by dropping the ref \nusing xe_bo_put_deferred(), and moving the final commit outside of the \nlock. Dropping the lock around the put is tricky since the bo can go \nout of scope and delete itself from the list, making it difficult to \nnavigate to the next list entry. \n \n(cherry picked from commit 0083b8e6f11d7662283a267d4ce7c966812ffd8a) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:30.000000Z"} {"uuid": "f0f6f5bf-5c28-4283-8f8b-ae7eba05d743", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46867", "type": "seen", "source": "https://t.me/cvedetector/6524", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46867 - Linux Kernel X.Org drm Atomic Sleeping Lock Deadlock\", \n \"Content\": \"CVE ID : CVE-2024-46867 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/xe/client: fix deadlock in show_meminfo() \n \nThere is a real deadlock as well as sleeping in atomic() bug in here, if \nthe bo put happens to be the last ref, since bo destruction wants to \ngrab the same spinlock and sleeping locks. Fix that by dropping the ref \nusing xe_bo_put_deferred(), and moving the final commit outside of the \nlock. Dropping the lock around the put is tricky since the bo can go \nout of scope and delete itself from the list, making it difficult to \nnavigate to the next list entry. \n \n(cherry picked from commit 0083b8e6f11d7662283a267d4ce7c966812ffd8a) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:30.000000Z"} https://db.gcve.eu/sighting/f0f6f5bf-5c28-4283-8f8b-ae7eba05d743/export Fri, 27 Sep 2024 15:53:30 +0000 https://db.gcve.eu/sighting/40ff810e-0b3b-4c52-b4ce-8ef23c441b67/export {"uuid": "40ff810e-0b3b-4c52-b4ce-8ef23c441b67", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46869", "type": "seen", "source": "https://t.me/cvedetector/6661", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46869 - Linux Bluetooth - Memory Allocation Bug\", \n \"Content\": \"CVE ID : CVE-2024-46869 \nPublished : Sept. 30, 2024, 4:15 p.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nBluetooth: btintel_pcie: Allocate memory for driver private data \n \nFix driver not allocating memory for struct btintel_data which is used \nto store internal data. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"30 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-30T19:10:01.000000Z"} {"uuid": "40ff810e-0b3b-4c52-b4ce-8ef23c441b67", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46869", "type": "seen", "source": "https://t.me/cvedetector/6661", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46869 - Linux Bluetooth - Memory Allocation Bug\", \n \"Content\": \"CVE ID : CVE-2024-46869 \nPublished : Sept. 30, 2024, 4:15 p.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nBluetooth: btintel_pcie: Allocate memory for driver private data \n \nFix driver not allocating memory for struct btintel_data which is used \nto store internal data. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"30 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-30T19:10:01.000000Z"} https://db.gcve.eu/sighting/40ff810e-0b3b-4c52-b4ce-8ef23c441b67/export Mon, 30 Sep 2024 19:10:01 +0000 https://db.gcve.eu/sighting/2b9a93bd-c567-4880-bf39-5c6a9b7125a7/export {"uuid": "2b9a93bd-c567-4880-bf39-5c6a9b7125a7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-4686", "type": "seen", "source": "Telegram/k8Bduzb4Su_Gx_jeNQZ8NpCxkb6ZqwHtYnfi715qw88lGWKf", "content": "", "creation_timestamp": "2025-02-19T22:21:29.000000Z"} {"uuid": "2b9a93bd-c567-4880-bf39-5c6a9b7125a7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-4686", "type": "seen", "source": "Telegram/k8Bduzb4Su_Gx_jeNQZ8NpCxkb6ZqwHtYnfi715qw88lGWKf", "content": "", "creation_timestamp": "2025-02-19T22:21:29.000000Z"} https://db.gcve.eu/sighting/2b9a93bd-c567-4880-bf39-5c6a9b7125a7/export Wed, 19 Feb 2025 22:21:29 +0000 https://db.gcve.eu/sighting/f0ef51ac-9ced-47c9-8e4e-e6ebe0112ec5/export {"uuid": "f0ef51ac-9ced-47c9-8e4e-e6ebe0112ec5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46860", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "f0ef51ac-9ced-47c9-8e4e-e6ebe0112ec5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46860", "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/f0ef51ac-9ced-47c9-8e4e-e6ebe0112ec5/export Wed, 03 Dec 2025 14:14:49 +0000 https://db.gcve.eu/sighting/77c81093-8c44-4ad4-9623-363a5be06179/export {"uuid": "77c81093-8c44-4ad4-9623-363a5be06179", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-46861", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "77c81093-8c44-4ad4-9623-363a5be06179", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-46861", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} https://db.gcve.eu/sighting/77c81093-8c44-4ad4-9623-363a5be06179/export Thu, 19 Mar 2026 00:00:00 +0000 https://db.gcve.eu/sighting/14b3e94b-8567-4fd1-a821-318874cb4118/export {"uuid": "14b3e94b-8567-4fd1-a821-318874cb4118", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-46860", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "14b3e94b-8567-4fd1-a821-318874cb4118", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-46860", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} https://db.gcve.eu/sighting/14b3e94b-8567-4fd1-a821-318874cb4118/export Thu, 19 Mar 2026 00:00:00 +0000