CVE-2024-36939

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.2% (14th 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

Also known asEUVD-2024-36289 (ENISA EUVD)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.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

nfs: Handle error of rpc_proc_register() in nfs_net_init().

syzkaller reported a warning [0] triggered while destroying immature netns.

rpc_proc_register() was called in init_nfs_fs(), but its error has been ignored since at least the initial commit 1da177e4c3f4 ("Linux-2.6.12-rc2").

Recently, commit d47151b79e32 ("nfs: expose /proc/net/sunrpc/nfs in net namespaces") converted the procfs to per-netns and made the problem more visible.

Even when rpc_proc_register() fails, nfs_net_init() could succeed, and thus nfs_net_exit() will be called while destroying the netns.

Then, remove_proc_entry() will be called for non-existing proc directory and trigger the warning below.

Let's handle the error of rpc_proc_register() properly in nfs_net_init().

[0]: name 'nfs' WARNING: CPU: 1 PID: 1710 at fs/proc/generic.c:711 remove_proc_entry+0x1bb/0x2d0 fs/proc/generic.c:711 Modules linked in: CPU: 1 PID: 1710 Comm: syz-executor.2 Not tainted 6.8.0-12822-gcd51db110a7e #12 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:remove_proc_entry+0x1bb/0x2d0 fs/proc/generic.c:711 Code: 41 5d 41 5e c3 e8 85 09 b5 ff 48 c7 c7 88 58 64 86 e8 09 0e 71 02 e8 74 09 b5 ff 4c 89 e6 48 c7 c7 de 1b 80 84 e8 c5 ad 97 ff <0f> 0b eb b1 e8 5c 09 b5 ff 48 c7 c7 88 58 64 86 e8 e0 0d 71 02 eb RSP: 0018:ffffc9000c6d7ce0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: ffff8880422b8b00 RCX: ffffffff8110503c RDX: ffff888030652f00 RSI: ffffffff81105045 RDI: 0000000000000001 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000001 R11: ffffffff81bb62cb R12: ffffffff84807ffc R13: ffff88804ad6fcc0 R14: ffffffff84807ffc R15: ffffffff85741ff8 FS: 00007f30cfba8640(0000) GS:ffff88807dd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ff51afe8000 CR3: 000000005a60a005 CR4: 0000000000770ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: rpc_proc_unregister+0x64/0x70 net/sunrpc/stats.c:310 nfs_net_exit+0x1c/0x30 fs/nfs/inode.c:2438 ops_exit_list+0x62/0xb0 net/core/net_namespace.c:170 setup_net+0x46c/0x660 net/core/net_namespace.c:372 copy_net_ns+0x244/0x590 net/core/net_namespace.c:505 create_new_namespaces+0x2ed/0x770 kernel/nsproxy.c:110 unshare_nsproxy_namespaces+0xae/0x160 kernel/nsproxy.c:228 ksys_unshare+0x342/0x760 kernel/fork.c:3322 __do_sys_unshare kernel/fork.c:3393 [inline] __se_sys_unshare kernel/fork.c:3391 [inline] __x64_sys_unshare+0x1f/0x30 kernel/fork.c:3391 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x4f/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x46/0x4e RIP: 0033:0x7f30d0febe5d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 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 8b 0d 73 9f 1b 00 f7 d8 64 89 01 48 RSP: 002b:00007f30cfba7cc8 EFLAGS: 00000246 ORIG_RAX: 0000000000000110 RAX: ffffffffffffffda RBX: 00000000004bbf80 RCX: 00007f30d0febe5d RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000006c020600 RBP: 00000000004bbf80 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002 R13: 000000000000000b R14: 00007f30d104c530 R15: 0000000000000000

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.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
14th
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.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

May 30, 2024

Last Modified

October 15, 2026

References (9)

Vendor Advisories for CVE-2024-36939(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-raspi-hwe-18.04-edge (5.4.0.1114.126~18.04.1) @ bionic2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1070.68) @ jammy2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1049 (5.4.0-1049.53) @ focal2026-10-15ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-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-virtual-hwe-20.04-edge (5.15.0.118.118) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1065.61) @ jammy2026-10-15ubuntu
ubuntulinux-tools-bluefield (5.4.0.1090.86) @ focal2026-10-15ubuntu
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1135.129) @ focal2026-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-oem-24.04a (6.8.0-1010.10) @ noble2026-10-15ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1060.58) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1129.122) @ focal2026-10-15ubuntu
redhatkernel-0:5.14.0-427.65.1.el9_42025-04-16redhat
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
redhatkernel-0:4.18.0-553.22.1.el8_102024-09-24redhat
redhatkernel-rt-0:4.18.0-553.22.1.rt7.363.el8_102024-09-24redhat
linuxKernel @ 5.4.276 (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

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
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
—

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 96 of 234 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 138 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2024-36939?
CVE-2024-36939 is a medium-severity vulnerability; its CVE record was published on May 30, 2024. In the Linux kernel, the following vulnerability has been resolved: nfs: Handle error of rpc_proc_register() in nfs_net_init(). syzkaller reported a warning [0] triggered while destroying immature netns. rpc_proc_register() was called in init_nfs_fs(), but its error has been ignored since at least…
When was the CVE record for CVE-2024-36939 published?
The CVE record for CVE-2024-36939 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-36939 actively exploited?
CVE-2024-36939 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-36939?
CVE-2024-36939 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-36939?
A fix for CVE-2024-36939 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-36939 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-36939

Explore →

Is Your Infrastructure Affected by CVE-2024-36939?

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

Book a Demo →Browse All CVEs