CVE-2024-53100

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

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

Score 4.7 from GitHub Security Advisory published 2024-11-26. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-50516 (ENISA EUVD) · GHSA-mh5g-qxxq-3x3p (GitHub Security Advisories)Source: ENISA EUVD

4.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

nvme: tcp: avoid race between queue_lock lock and destroy

Commit 76d54bf20cdc ("nvme-tcp: don't access released socket during error recovery") added a mutex_lock() call for the queue->queue_lock in nvme_tcp_get_address(). However, the mutex_lock() races with mutex_destroy() in nvme_tcp_free_queue(), and causes the WARN below.

DEBUG_LOCKS_WARN_ON(lock->magic != lock) WARNING: CPU: 3 PID: 34077 at kernel/locking/mutex.c:587 __mutex_lock+0xcf0/0x1220 Modules linked in: nvmet_tcp nvmet nvme_tcp nvme_fabrics iw_cm ib_cm ib_core pktcdvd nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables qrtr sunrpc ppdev 9pnet_virtio 9pnet pcspkr netfs parport_pc parport e1000 i2c_piix4 i2c_smbus loop fuse nfnetlink zram bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper xfs drm sym53c8xx floppy nvme scsi_transport_spi nvme_core nvme_auth serio_raw ata_generic pata_acpi dm_multipath qemu_fw_cfg [last unloaded: ib_uverbs] CPU: 3 UID: 0 PID: 34077 Comm: udisksd Not tainted 6.11.0-rc7 #319 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014 RIP: 0010:__mutex_lock+0xcf0/0x1220 Code: 08 84 d2 0f 85 c8 04 00 00 8b 15 ef b6 c8 01 85 d2 0f 85 78 f4 ff ff 48 c7 c6 20 93 ee af 48 c7 c7 60 91 ee af e8 f0 a7 6d fd <0f> 0b e9 5e f4 ff ff 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 RSP: 0018:ffff88811305f760 EFLAGS: 00010286 RAX: 0000000000000000 RBX: ffff88812c652058 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000001 RBP: ffff88811305f8b0 R08: 0000000000000001 R09: ffffed1075c36341 R10: ffff8883ae1b1a0b R11: 0000000000010498 R12: 0000000000000000 R13: 0000000000000000 R14: dffffc0000000000 R15: ffff88812c652058 FS: 00007f9713ae4980(0000) GS:ffff8883ae180000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcd78483c7c CR3: 0000000122c38000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ? __warn.cold+0x5b/0x1af ? __mutex_lock+0xcf0/0x1220 ? report_bug+0x1ec/0x390 ? handle_bug+0x3c/0x80 ? exc_invalid_op+0x13/0x40 ? asm_exc_invalid_op+0x16/0x20 ? __mutex_lock+0xcf0/0x1220 ? nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp] ? __pfx___mutex_lock+0x10/0x10 ? __lock_acquire+0xd6a/0x59e0 ? nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp] nvme_tcp_get_address+0xc2/0x1e0 [nvme_tcp] ? __pfx_nvme_tcp_get_address+0x10/0x10 [nvme_tcp] nvme_sysfs_show_address+0x81/0xc0 [nvme_core] dev_attr_show+0x42/0x80 ? __asan_memset+0x1f/0x40 sysfs_kf_seq_show+0x1f0/0x370 seq_read_iter+0x2cb/0x1130 ? rw_verify_area+0x3b1/0x590 ? __mutex_lock+0x433/0x1220 vfs_read+0x6a6/0xa20 ? lockdep_hardirqs_on+0x78/0x100 ? __pfx_vfs_read+0x10/0x10 ksys_read+0xf7/0x1d0 ? __pfx_ksys_read+0x10/0x10 ? __x64_sys_openat+0x105/0x1d0 do_syscall_64+0x93/0x180 ? lockdep_hardirqs_on_prepare+0x16d/0x400 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on+0x78/0x100 ? do_syscall_64+0x9f/0x180 ? __pfx_ksys_read+0x10/0x10 ? lockdep_hardirqs_on_prepare+0x16d/0x400 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on+0x78/0x100 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on_prepare+0x16d/0x400 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on+0x78/0x100 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on_prepare+0x16d/0x400 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on+0x78/0x100 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on_prepare+0x16d/0x400 ? do_syscall_64+0x9f/0x180 ? lockdep_hardirqs_on+0x78/0x100 ? do_syscall_64+0x9f/0x180 ? do_syscall_64+0x9f/0x180 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f9713f55cfa Code: 55 48 89 e5 48 83 ec 20 48 89 55 e8 48 89 75 f0 89 7d f8 e8 e8 74 f8 ff 48 8b 55 e8 48 8b 75 f0 4 ---truncated---

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.2%
EPSS %ILE
6th
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 (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

November 25, 2024

Last Modified

August 5, 2026

References (4)

Vendor Advisories for CVE-2024-53100(1)

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-24ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-24ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-24ubuntu
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-10-24ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-10-24ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-24ubuntu
linuxKernel @ 6.1.118 (fixes >=5.0.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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1
  • every version up to 6.1.119-1~deb11u1: fixed in 6.1.119-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (31 versions)
  • every version up to 6.1.119-1: fixed in 6.1.119-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.9-1: fixed in 6.11.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.9-1: fixed in 6.11.9-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 7× in last 7d / 39× 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 210 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 115 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.2% · 6th percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-25 16:57 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-24 03:21 UTCEG score recompute
  13. 2026-10-24 03:21 UTCVendor advisory
  14. 2026-10-24 03:20 UTCGHSA enrichmentGHSA-mh5g-qxxq-3x3p · GitHub CVSS 4.7
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-19 17:55 UTCOSV refresh
  20. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-10-18 06:51 UTCEG score recompute
  23. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 70 more
  1. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-12 17:39 UTCEG score recompute
  4. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-11 21:05 UTCEG score recompute
  6. 2026-10-11 15:57 UTCEG score recompute
  7. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-02 16:21 UTCEG score recompute
  17. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-09-26 22:42 UTCOSV refresh
  22. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  33. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  37. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-09-07 08:48 UTCOSV refresh
  39. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  41. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  42. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  43. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  44. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  45. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  46. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  47. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  48. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  49. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  50. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  51. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  52. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  53. 2026-08-20 18:01 UTCOSV refresh
  54. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  55. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  56. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  57. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  58. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  59. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  60. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  61. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  62. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  63. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  64. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  65. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  66. 2026-08-05 11:52 UTCEG score recompute
  67. 2026-08-05 11:52 UTCVendor advisory
  68. 2026-08-05 11:52 UTCGHSA enrichmentGHSA-mh5g-qxxq-3x3p · GitHub CVSS 4.7
  69. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  70. 2026-08-04 11:23 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-53100?
CVE-2024-53100 is a medium-severity vulnerability; its CVE record was published on November 25, 2024. In the Linux kernel, the following vulnerability has been resolved: nvme: tcp: avoid race between queue_lock lock and destroy Commit 76d54bf20cdc ("nvme-tcp: don't access released socket during error recovery") added a mutex_lock() call for the queue->queue_lock in nvme_tcp_get_address(). However,…
When was the CVE record for CVE-2024-53100 published?
The CVE record for CVE-2024-53100 was published on November 25, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-53100 actively exploited?
CVE-2024-53100 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-53100?
CVE-2024-53100 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2024-53100?
A fix for CVE-2024-53100 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-53100 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-53100

Explore →

Is Your Infrastructure Affected by CVE-2024-53100?

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

Book a Demo →Browse All CVEs