CVE-2024-44946

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2024-08-31. NVD baseline CVSS 5.5; sources differ by 0.0.

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

Also known asEUVD-2024-41246 (ENISA EUVD) · GHSA-cw5c-5w4g-ff67 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
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.9%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

kcm: Serialise kcm_sendmsg() for the same socket.

syzkaller reported UAF in kcm_release(). [0]

The scenario is

  • Thread A builds a skb with MSG_MORE and sets kcm->seq_skb.
  • Thread A resumes building skb from kcm->seq_skb but is blocked
by sk_stream_wait_memory()
  • Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb
and puts the skb to the write queue
  • Thread A faces an error and finally frees skb that is already in the
write queue
  • kcm_release() does double-free the skb in the write queue

When a thread is building a MSG_MORE skb, another thread must not touch it.

Let's add a per-sk mutex and serialise kcm_sendmsg().

[0]: BUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge include/linux/skbuff.h:3181 [inline] BUG: KASAN: slab-use-after-free in kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691 Read of size 8 at addr ffff0000ced0fc80 by task syz-executor329/6167

CPU: 1 PID: 6167 Comm: syz-executor329 Tainted: G B 6.8.0-rc5-syzkaller-g9abbc24128bc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:291 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:298 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:377 [inline] print_report+0x178/0x518 mm/kasan/report.c:488 kasan_report+0xd8/0x138 mm/kasan/report.c:601 __asan_report_load8_noabort+0x20/0x2c mm/kasan/report_generic.c:381 __skb_unlink include/linux/skbuff.h:2366 [inline] __skb_dequeue include/linux/skbuff.h:2385 [inline] __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] __skb_queue_purge include/linux/skbuff.h:3181 [inline] kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691 __sock_release net/socket.c:659 [inline] sock_close+0xa4/0x1e8 net/socket.c:1421 __fput+0x30c/0x738 fs/file_table.c:376 ____fput+0x20/0x30 fs/file_table.c:404 task_work_run+0x230/0x2e0 kernel/task_work.c:180 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0x618/0x1f64 kernel/exit.c:871 do_group_exit+0x194/0x22c kernel/exit.c:1020 get_signal+0x1500/0x15ec kernel/signal.c:2893 do_signal+0x23c/0x3b44 arch/arm64/kernel/signal.c:1249 do_notify_resume+0x74/0x1f4 arch/arm64/kernel/entry-common.c:148 exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline] exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline] el0_svc+0xac/0x168 arch/arm64/kernel/entry-common.c:713 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598

Allocated by task 6166: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x40/0x78 mm/kasan/common.c:68 kasan_save_alloc_info+0x70/0x84 mm/kasan/generic.c:626 unpoison_slab_object mm/kasan/common.c:314 [inline] __kasan_slab_alloc+0x74/0x8c mm/kasan/common.c:340 kasan_slab_alloc include/linux/kasan.h:201 [inline] slab_post_alloc_hook mm/slub.c:3813 [inline] slab_alloc_node mm/slub.c:3860 [inline] kmem_cache_alloc_node+0x204/0x4c0 mm/slub.c:3903 __alloc_skb+0x19c/0x3d8 net/core/skbuff.c:641 alloc_skb include/linux/skbuff.h:1296 [inline] kcm_sendmsg+0x1d3c/0x2124 net/kcm/kcmsock.c:783 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg net/socket.c:745 [inline] sock_sendmsg+0x220/0x2c0 net/socket.c:768 splice_to_socket+0x7cc/0xd58 fs/splice.c:889 do_splice_from fs/splice.c:941 [inline] direct_splice_actor+0xec/0x1d8 fs/splice.c:1164 splice_direct_to_actor+0x438/0xa0c fs/splice.c:1108 do_splice_direct_actor ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 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.9%
EPSS %ILE
58th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% 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

August 31, 2024

Last Modified

August 5, 2026

References (8)

Vendor Advisories for CVE-2024-44946(1)

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

Patch Availability(17)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04 (6.8.0-50.51) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.200.220~18.04.1) @ bionic2026-10-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1054 (5.4.0-1054.58) @ focal2026-10-24ubuntu
ubuntulinux-tools-azure (6.8.0-1020.23) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1078.87~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-tools-bluefield (5.4.0.1094.90) @ focal2026-10-24ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1134.143~18.04.1) @ bionic2026-10-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1038.42) @ jammy2026-10-24ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1072.72) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1075.73) @ jammy2026-10-24ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1119.149) @ focal2026-10-24ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1067.67) @ jammy2026-10-24ubuntu
ubuntulinux-tools-iot (5.4.0.1044.42) @ focal2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1019.21.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy2026-10-24ubuntu
linuxKernel @ 4.19.321 (fixes >=4.6.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 ... 5.10.92-2 (43 versions)
  • every version up to 5.10.226-1: fixed in 5.10.226-1
—
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 (29 versions)
  • every version up to 6.1.112-1: fixed in 6.1.112-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.7-1: fixed in 6.10.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.7-1: fixed in 6.10.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(16)

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 96 of 214 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 118 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.9% · 58th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  9. 2026-10-25 17:02 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  11. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  12. 2026-10-24 05:13 UTCEG score recompute
  13. 2026-10-24 05:13 UTCVendor advisory
  14. 2026-10-24 05:13 UTCGHSA enrichmentGHSA-cw5c-5w4g-ff67 · GitHub CVSS 5.5
  15. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  19. 2026-10-19 18:55 UTCOSV refresh
  20. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  21. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  22. 2026-10-18 07:00 UTCEG score recompute
  23. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  24. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  25. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.9% · 57th percentile
Show 71 more
  1. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  2. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  3. 2026-10-12 17:45 UTCEG score recompute
  4. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  5. 2026-10-11 21:11 UTCEG score recompute
  6. 2026-10-11 16:03 UTCEG score recompute
  7. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  8. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  10. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  12. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  16. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  17. 2026-09-30 19:53 UTCEG score recompute
  18. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  19. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  21. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  22. 2026-09-27 00:11 UTCOSV refresh
  23. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  24. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  26. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  27. 2026-09-21 20:32 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  28. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  29. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  30. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  31. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  32. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  33. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  34. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  35. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  36. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  37. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  38. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  39. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  40. 2026-09-07 09:18 UTCOSV refresh
  41. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  42. 2026-09-05 15:27 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  43. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  44. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  45. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  46. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  47. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  48. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  49. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  50. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  51. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  52. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  53. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  54. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  55. 2026-08-20 18:31 UTCOSV refresh
  56. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  57. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  58. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  59. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  61. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  62. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  63. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  64. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  65. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  66. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  67. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  68. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  69. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  70. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  71. 2026-08-05 12:03 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-44946?
CVE-2024-44946 is a medium-severity vulnerability; its CVE record was published on August 31, 2024. In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is…
When was the CVE record for CVE-2024-44946 published?
The CVE record for CVE-2024-44946 was published on August 31, 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-44946 actively exploited?
CVE-2024-44946 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-44946?
CVE-2024-44946 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-44946?
A fix for CVE-2024-44946 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-44946 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-44946

Explore →

Is Your Infrastructure Affected by CVE-2024-44946?

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

Book a Demo →Browse All CVEs