CVE-2024-36905

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (25th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
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.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets

TCP_SYN_RECV state is really special, it is only used by cross-syn connections, mostly used by fuzzers.

In the following crash [1], syzbot managed to trigger a divide by zero in tcp_rcv_space_adjust()

A socket makes the following state transitions, without ever calling tcp_init_transfer(), meaning tcp_init_buffer_space() is also not called.

TCP_CLOSE connect() TCP_SYN_SENT TCP_SYN_RECV shutdown() -> tcp_shutdown(sk, SEND_SHUTDOWN) TCP_FIN_WAIT1

To fix this issue, change tcp_shutdown() to not perform a TCP_SYN_RECV -> TCP_FIN_WAIT1 transition, which makes no sense anyway.

When tcp_rcv_state_process() later changes socket state from TCP_SYN_RECV to TCP_ESTABLISH, then look at sk->sk_shutdown to finally enter TCP_FIN_WAIT1 state, and send a FIN packet from a sane socket state.

This means tcp_send_fin() can now be called from BH context, and must use GFP_ATOMIC allocations.

[1] divide error: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 1 PID: 5084 Comm: syz-executor358 Not tainted 6.9.0-rc6-syzkaller-00022-g98369dccd2f8 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 RIP: 0010:tcp_rcv_space_adjust+0x2df/0x890 net/ipv4/tcp_input.c:767 Code: e3 04 4c 01 eb 48 8b 44 24 38 0f b6 04 10 84 c0 49 89 d5 0f 85 a5 03 00 00 41 8b 8e c8 09 00 00 89 e8 29 c8 48 0f af c3 31 d2 <48> f7 f1 48 8d 1c 43 49 8d 96 76 08 00 00 48 89 d0 48 c1 e8 03 48 RSP: 0018:ffffc900031ef3f0 EFLAGS: 00010246 RAX: 0c677a10441f8f42 RBX: 000000004fb95e7e RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: 0000000027d4b11f R08: ffffffff89e535a4 R09: 1ffffffff25e6ab7 R10: dffffc0000000000 R11: ffffffff8135e920 R12: ffff88802a9f8d30 R13: dffffc0000000000 R14: ffff88802a9f8d00 R15: 1ffff1100553f2da FS: 00005555775c0380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1155bf2304 CR3: 000000002b9f2000 CR4: 0000000000350ef0 Call Trace: tcp_recvmsg_locked+0x106d/0x25a0 net/ipv4/tcp.c:2513 tcp_recvmsg+0x25d/0x920 net/ipv4/tcp.c:2578 inet6_recvmsg+0x16a/0x730 net/ipv6/af_inet6.c:680 sock_recvmsg_nosec net/socket.c:1046 [inline] sock_recvmsg+0x109/0x280 net/socket.c:1068 ____sys_recvmsg+0x1db/0x470 net/socket.c:2803 ___sys_recvmsg net/socket.c:2845 [inline] do_recvmmsg+0x474/0xae0 net/socket.c:2939 __sys_recvmmsg net/socket.c:3018 [inline] __do_sys_recvmmsg net/socket.c:3041 [inline] __se_sys_recvmmsg net/socket.c:3034 [inline] __x64_sys_recvmmsg+0x199/0x250 net/socket.c:3034 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7faeb6363db9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffcc1997168 EFLAGS: 00000246 ORIG_RAX: 000000000000012b RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007faeb6363db9 RDX: 0000000000000001 RSI: 0000000020000bc0 RDI: 0000000000000005 RBP: 0000000000000000 R08: 0000000000000000 R09: 000000000000001c R10: 0000000000000122 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001

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.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 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.3%
EPSS %ILE
25th
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.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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: 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.

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

May 30, 2024

Last Modified

October 15, 2026

References (24)

15 of 24 shown · show the other 9

Vendor Advisories for CVE-2024-36905(4)

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

Patch Availability(23)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1065.61) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1135.129) @ focal2026-10-15ubuntu
ubuntulinux-tools-bluefield (5.4.0.1090.86) @ focal2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-10-15ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1060.58) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure (6.8.0-1012.14) @ noble2026-10-15ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.128~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-10-15ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-10-15ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-10-15ubuntu
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1049 (5.4.0-1049.53) @ focal2026-10-15ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.118) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1129.122) @ focal2026-10-15ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1070.68) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1065.71~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1135.142~18.04.1) @ bionic2026-10-15ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1114.126~18.04.1) @ bionic2026-10-15ubuntu
redhatkernel-0:5.14.0-427.57.1.el9_42025-03-05redhat
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat
redhatkernel-rt-0:4.18.0-553.16.1.rt7.357.el8_102024-08-08redhat
linuxKernel @ 4.19.314 (fixes >=2.6.12)—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

(6 across 5 ecosystems)
Debian:10(2)
PackageVulnerable rangeFix by version rangeDependents
linux4.19.118-1 ... 4.19.98-1~bpo9+1 (46 versions)
  • every version up to 4.19.316-1: fixed in 4.19.316-1
—
linux-5.105.10.136-1~deb10u1 ... 5.10.216-1~deb10u1 (14 versions)
  • every version up to 5.10.218-1~deb10u1: fixed in 5.10.218-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (40 versions)
  • every version up to 5.10.218-1: fixed in 5.10.218-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.94-1~bpo11+1 (23 versions)
  • every version up to 6.1.94-1: fixed in 6.1.94-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.11-1: fixed in 6.8.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.11-1: fixed in 6.8.11-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(18)

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 8× in last 7d / 38× 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 94 of 221 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-36905?
CVE-2024-36905 is a medium-severity vulnerability; its CVE record was published on May 30, 2024. In the Linux kernel, the following vulnerability has been resolved: tcp: defer shutdown(SENDSHUTDOWN) for TCPSYN_RECV sockets TCPSYNRECV state is really special, it is only used by cross-syn connections, mostly used by fuzzers. In the following crash [1], syzbot managed to trigger a divide by zero…
When was the CVE record for CVE-2024-36905 published?
The CVE record for CVE-2024-36905 was published on May 30, 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-36905 actively exploited?
CVE-2024-36905 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-36905?
CVE-2024-36905 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-36905?
A fix for CVE-2024-36905 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-36905 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-36905

Explore →

Is Your Infrastructure Affected by CVE-2024-36905?

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

Book a Demo →Browse All CVEs