CVE-2024-36933

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% (21st 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
Trending — 3 sources updated this week
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:

nsh: Restore skb->{protocol,data,mac_header} for outer header in nsh_gso_segment().

syzbot triggered various splats (see [0] and links) by a crafted GSO packet of VIRTIO_NET_HDR_GSO_UDP layering the following protocols:

ETH_P_8021AD + ETH_P_NSH + ETH_P_IPV6 + IPPROTO_UDP

NSH can encapsulate IPv4, IPv6, Ethernet, NSH, and MPLS. As the inner protocol can be Ethernet, NSH GSO handler, nsh_gso_segment(), calls skb_mac_gso_segment() to invoke inner protocol GSO handlers.

nsh_gso_segment() does the following for the original skb before calling skb_mac_gso_segment()

  • reset skb->network_header
  • save the original skb->{mac_heaeder,mac_len} in a local variable
  • pull the NSH header
  • resets skb->mac_header
  • set up skb->mac_len and skb->protocol for the inner protocol.

and does the following for the segmented skb

  • set ntohs(ETH_P_NSH) to skb->protocol
  • push the NSH header
  • restore skb->mac_header
  • set skb->mac_header + mac_len to skb->network_header
  • restore skb->mac_len

There are two problems in 6-7 and 8-9.

(a) After 6 & 7, skb->data points to the NSH header, so the outer header (ETH_P_8021AD in this case) is stripped when skb is sent out of netdev.

Also, if NSH is encapsulated by NSH + Ethernet (so NSH-Ethernet-NSH), skb_pull() in the first nsh_gso_segment() will make skb->data point to the middle of the outer NSH or Ethernet header because the Ethernet header is not pulled by the second nsh_gso_segment().

(b) While restoring skb->{mac_header,network_header} in 8 & 9, nsh_gso_segment() does not assume that the data in the linear buffer is shifted.

However, udp6_ufo_fragment() could shift the data and change skb->mac_header accordingly as demonstrated by syzbot.

If this happens, even the restored skb->mac_header points to the middle of the outer header.

It seems nsh_gso_segment() has never worked with outer headers so far.

At the end of nsh_gso_segment(), the outer header must be restored for the segmented skb, instead of the NSH header.

To do that, let's calculate the outer header position relatively from the inner header and set skb->{data,mac_header,protocol} properly.

[0]: BUG: KMSAN: uninit-value in ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:524 [inline] BUG: KMSAN: uninit-value in ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline] BUG: KMSAN: uninit-value in ipvlan_queue_xmit+0xf44/0x16b0 drivers/net/ipvlan/ipvlan_core.c:668 ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:524 [inline] ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline] ipvlan_queue_xmit+0xf44/0x16b0 drivers/net/ipvlan/ipvlan_core.c:668 ipvlan_start_xmit+0x5c/0x1a0 drivers/net/ipvlan/ipvlan_main.c:222 __netdev_start_xmit include/linux/netdevice.h:4989 [inline] netdev_start_xmit include/linux/netdevice.h:5003 [inline] xmit_one net/core/dev.c:3547 [inline] dev_hard_start_xmit+0x244/0xa10 net/core/dev.c:3563 __dev_queue_xmit+0x33ed/0x51c0 net/core/dev.c:4351 dev_queue_xmit include/linux/netdevice.h:3171 [inline] packet_xmit+0x9c/0x6b0 net/packet/af_packet.c:276 packet_snd net/packet/af_packet.c:3081 [inline] packet_sendmsg+0x8aef/0x9f10 net/packet/af_packet.c:3113 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg net/socket.c:745 [inline] __sys_sendto+0x735/0xa10 net/socket.c:2191 __do_sys_sendto net/socket.c:2203 [inline] __se_sys_sendto net/socket.c:2199 [inline] __x64_sys_sendto+0x125/0x1c0 net/socket.c:2199 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b

Uninit was created at: slab_post_alloc_hook mm/slub.c:3819 [inline] slab_alloc_node mm/slub.c:3860 [inline] __do_kmalloc_node mm/slub.c:3980 [inline] __kmalloc_node_track_caller+0x705/0x1000 mm/slub.c:4001 kmalloc_reserve+0x249/0x4a0 net/core/skbuff.c:582 __ ---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.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
21st
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

August 5, 2026

Patch Availability(22)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-05-24ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1065.61) @ jammy2026-05-24ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1129.122) @ focal2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.118) @ jammy2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1049 (5.4.0-1049.53) @ focal2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.128~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1135.142~18.04.1) @ bionic2026-05-24ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1135.129) @ focal2026-05-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1060.58) @ jammy2026-05-24ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1065.71~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-bluefield (5.4.0.1090.86) @ focal2026-05-24ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1114.126~18.04.1) @ bionic2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-05-24ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-05-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-05-24ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1070.68) @ jammy2026-05-24ubuntu
redhatkernel-0:5.14.0-427.72.1.el9_42025-06-11redhat
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 >=4.14.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

(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

(17)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2024-36933?
CVE-2024-36933 is a medium-severity vulnerability; its CVE record was published on May 30, 2024. In the Linux kernel, the following vulnerability has been resolved: nsh: Restore skb->{protocol,data,macheader} for outer header in nshgso_segment(). syzbot triggered various splats (see [0] and links) by a crafted GSO packet of VIRTIONETHDRGSOUDP layering the following protocols: ETHP8021AD +…
When was the CVE record for CVE-2024-36933 published?
The CVE record for CVE-2024-36933 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-36933 actively exploited?
CVE-2024-36933 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-36933?
CVE-2024-36933 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-36933?
A fix for CVE-2024-36933 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-36933 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-36933

Explore →

Is Your Infrastructure Affected by CVE-2024-36933?

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