CVE-2024-53166

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-12-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-51838 (ENISA EUVD) · GHSA-6gmm-x3pr-vhmf (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

block, bfq: fix bfqq uaf in bfq_limit_depth()

Set new allocated bfqq to bic or remove freed bfqq from bic are both protected by bfqd->lock, however bfq_limit_depth() is deferencing bfqq from bic without the lock, this can lead to UAF if the io_context is shared by multiple tasks.

For example, test bfq with io_uring can trigger following UAF in v6.6:

================================================================== BUG: KASAN: slab-use-after-free in bfqq_group+0x15/0x50

Call Trace: dump_stack_lvl+0x47/0x80 print_address_description.constprop.0+0x66/0x300 print_report+0x3e/0x70 kasan_report+0xb4/0xf0 bfqq_group+0x15/0x50 bfqq_request_over_limit+0x130/0x9a0 bfq_limit_depth+0x1b5/0x480 __blk_mq_alloc_requests+0x2b5/0xa00 blk_mq_get_new_requests+0x11d/0x1d0 blk_mq_submit_bio+0x286/0xb00 submit_bio_noacct_nocheck+0x331/0x400 __block_write_full_folio+0x3d0/0x640 writepage_cb+0x3b/0xc0 write_cache_pages+0x254/0x6c0 write_cache_pages+0x254/0x6c0 do_writepages+0x192/0x310 filemap_fdatawrite_wbc+0x95/0xc0 __filemap_fdatawrite_range+0x99/0xd0 filemap_write_and_wait_range.part.0+0x4d/0xa0 blkdev_read_iter+0xef/0x1e0 io_read+0x1b6/0x8a0 io_issue_sqe+0x87/0x300 io_wq_submit_work+0xeb/0x390 io_worker_handle_work+0x24d/0x550 io_wq_worker+0x27f/0x6c0 ret_from_fork_asm+0x1b/0x30

Allocated by task 808602: kasan_save_stack+0x1e/0x40 kasan_set_track+0x21/0x30 __kasan_slab_alloc+0x83/0x90 kmem_cache_alloc_node+0x1b1/0x6d0 bfq_get_queue+0x138/0xfa0 bfq_get_bfqq_handle_split+0xe3/0x2c0 bfq_init_rq+0x196/0xbb0 bfq_insert_request.isra.0+0xb5/0x480 bfq_insert_requests+0x156/0x180 blk_mq_insert_request+0x15d/0x440 blk_mq_submit_bio+0x8a4/0xb00 submit_bio_noacct_nocheck+0x331/0x400 __blkdev_direct_IO_async+0x2dd/0x330 blkdev_write_iter+0x39a/0x450 io_write+0x22a/0x840 io_issue_sqe+0x87/0x300 io_wq_submit_work+0xeb/0x390 io_worker_handle_work+0x24d/0x550 io_wq_worker+0x27f/0x6c0 ret_from_fork+0x2d/0x50 ret_from_fork_asm+0x1b/0x30

Freed by task 808589: kasan_save_stack+0x1e/0x40 kasan_set_track+0x21/0x30 kasan_save_free_info+0x27/0x40 __kasan_slab_free+0x126/0x1b0 kmem_cache_free+0x10c/0x750 bfq_put_queue+0x2dd/0x770 __bfq_insert_request.isra.0+0x155/0x7a0 bfq_insert_request.isra.0+0x122/0x480 bfq_insert_requests+0x156/0x180 blk_mq_dispatch_plug_list+0x528/0x7e0 blk_mq_flush_plug_list.part.0+0xe5/0x590 __blk_flush_plug+0x3b/0x90 blk_finish_plug+0x40/0x60 do_writepages+0x19d/0x310 filemap_fdatawrite_wbc+0x95/0xc0 __filemap_fdatawrite_range+0x99/0xd0 filemap_write_and_wait_range.part.0+0x4d/0xa0 blkdev_read_iter+0xef/0x1e0 io_read+0x1b6/0x8a0 io_issue_sqe+0x87/0x300 io_wq_submit_work+0xeb/0x390 io_worker_handle_work+0x24d/0x550 io_wq_worker+0x27f/0x6c0 ret_from_fork+0x2d/0x50 ret_from_fork_asm+0x1b/0x30

Fix the problem by protecting bic_to_bfqq() with bfqd->lock.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 27, 2024

Last Modified

October 15, 2026

Advisory Details (5)

Auto-updated Jul 14, 2026
Patch available.
Web page

block, bfq: fix bfqq uaf in bfq_limit_depth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e8b8344de3980709080d86c157d24e7de07d70ad
Web page

block, bfq: fix bfqq uaf in bfq_limit_depth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01a853faaeaf3379ccf358ade582b1d28752126e
Web page

block, bfq: fix bfqq uaf in bfq_limit_depth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dcaa738afde55085ac6056252e319479cf23cde2
Web page

block, bfq: fix bfqq uaf in bfq_limit_depth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/906cdbdd3b018ff69cc830173bce277a847d4fdc
Web page

block, bfq: fix bfqq uaf in bfq_limit_depth() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ada4ca5fd5a9d5212f28164d49a4885951c979c9

Vendor Advisories for CVE-2024-53166(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-28ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-28ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-28ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-10-28ubuntu
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-10-28ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-10-28ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-10-28ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-10-28ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-10-28ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-28ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-28ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-28ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 6.1.130 (fixes >=5.17.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.129-1~deb11u1 (7 versions)
  • every version up to 6.1.137-1~deb11u1: fixed in 6.1.137-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (36 versions)
  • every version up to 6.1.133-1: fixed in 6.1.133-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(12)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 233 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 138 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-28 17:11 UTCEG score recompute
  7. 2026-10-28 17:11 UTCVendor advisory
  8. 2026-10-28 17:11 UTCGHSA enrichmentGHSA-6gmm-x3pr-vhmf · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-10-25 16:57 UTCEG score recompute
  13. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-21 17:30 UTCEG score recompute
  18. 2026-10-21 17:30 UTCVendor advisory
  19. 2026-10-21 17:30 UTCGHSA enrichmentGHSA-6gmm-x3pr-vhmf · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  21. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  22. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  23. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  24. 2026-10-18 06:51 UTCEG score recompute
  25. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
Show 70 more
  1. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  2. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  3. 2026-10-15 01:28 UTCEG score recompute
  4. 2026-10-15 01:28 UTCVendor advisory
  5. 2026-10-15 01:28 UTCGHSA enrichmentGHSA-6gmm-x3pr-vhmf · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-10-15 01:08 UTCEG score recompute
  7. 2026-10-15 01:08 UTCVendor advisory
  8. 2026-10-15 01:07 UTCGHSA enrichmentGHSA-6gmm-x3pr-vhmf · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  10. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-12 17:39 UTCEG score recompute
  12. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-11 21:05 UTCEG score recompute
  14. 2026-10-11 15:57 UTCEG score recompute
  15. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  20. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  21. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  22. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  23. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  24. 2026-10-02 16:21 UTCEG score recompute
  25. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  26. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  27. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  28. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  29. 2026-09-26 22:41 UTCOSV refresh
  30. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  31. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  32. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  34. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  35. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  36. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  37. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  38. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  39. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  40. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  41. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  42. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  43. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  44. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  46. 2026-09-07 08:18 UTCOSV refresh
  47. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  48. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  50. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  51. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  52. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  54. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  56. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  57. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  58. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  59. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  60. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  61. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  62. 2026-08-20 18:01 UTCOSV refresh
  63. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  64. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  65. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  66. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  67. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  68. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  69. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  70. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.3% · 16th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-53166?
CVE-2024-53166 is a high-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix bfqq uaf in bfq_limit_depth() Set new allocated bfqq to bic or remove freed bfqq from bic are both protected by bfqd->lock, however bfq_limit_depth() is deferencing bfqq from bic without the lock, this can lead to…
When was the CVE record for CVE-2024-53166 published?
The CVE record for CVE-2024-53166 was published on December 27, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-53166 actively exploited?
CVE-2024-53166 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-53166?
CVE-2024-53166 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-53166?
A fix for CVE-2024-53166 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-53166 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-53166

Explore →

Is Your Infrastructure Affected by CVE-2024-53166?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs