CVE-2024-26636

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-03-18. 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-23898 (ENISA EUVD) · GHSA-33v3-2qxj-vgv5 (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.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:

llc: make llc_ui_sendmsg() more robust against bonding changes

syzbot was able to trick llc_ui_sendmsg(), allocating an skb with no headroom, but subsequently trying to push 14 bytes of Ethernet header [1]

Like some others, llc_ui_sendmsg() releases the socket lock before calling sock_alloc_send_skb(). Then it acquires it again, but does not redo all the sanity checks that were performed.

This fix:

  • Uses LL_RESERVED_SPACE() to reserve space.
  • Check all conditions again after socket lock is held again.
  • Do not account Ethernet header for mtu limitation.

[1]

skbuff: skb_under_panic: text:ffff800088baa334 len:1514 put:14 head:ffff0000c9c37000 data:ffff0000c9c36ff2 tail:0x5dc end:0x6c0 dev:bond0

kernel BUG at net/core/skbuff.c:193 ! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 0 PID: 6875 Comm: syz-executor.0 Not tainted 6.7.0-rc8-syzkaller-00101-g0802e17d9aca-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : skb_panic net/core/skbuff.c:189 [inline] pc : skb_under_panic+0x13c/0x140 net/core/skbuff.c:203 lr : skb_panic net/core/skbuff.c:189 [inline] lr : skb_under_panic+0x13c/0x140 net/core/skbuff.c:203 sp : ffff800096f97000 x29: ffff800096f97010 x28: ffff80008cc8d668 x27: dfff800000000000 x26: ffff0000cb970c90 x25: 00000000000005dc x24: ffff0000c9c36ff2 x23: ffff0000c9c37000 x22: 00000000000005ea x21: 00000000000006c0 x20: 000000000000000e x19: ffff800088baa334 x18: 1fffe000368261ce x17: ffff80008e4ed000 x16: ffff80008a8310f8 x15: 0000000000000001 x14: 1ffff00012df2d58 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000001 x10: 0000000000ff0100 x9 : e28a51f1087e8400 x8 : e28a51f1087e8400 x7 : ffff80008028f8d0 x6 : 0000000000000000 x5 : 0000000000000001 x4 : 0000000000000001 x3 : ffff800082b78714 x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000089 Call trace: skb_panic net/core/skbuff.c:189 [inline] skb_under_panic+0x13c/0x140 net/core/skbuff.c:203 skb_push+0xf0/0x108 net/core/skbuff.c:2451 eth_header+0x44/0x1f8 net/ethernet/eth.c:83 dev_hard_header include/linux/netdevice.h:3188 [inline] llc_mac_hdr_init+0x110/0x17c net/llc/llc_output.c:33 llc_sap_action_send_xid_c+0x170/0x344 net/llc/llc_s_ac.c:85 llc_exec_sap_trans_actions net/llc/llc_sap.c:153 [inline] llc_sap_next_state net/llc/llc_sap.c:182 [inline] llc_sap_state_process+0x1ec/0x774 net/llc/llc_sap.c:209 llc_build_and_send_xid_pkt+0x12c/0x1c0 net/llc/llc_sap.c:270 llc_ui_sendmsg+0x7bc/0xb1c net/llc/af_llc.c:997 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg net/socket.c:745 [inline] sock_sendmsg+0x194/0x274 net/socket.c:767 splice_to_socket+0x7cc/0xd58 fs/splice.c:881 do_splice_from fs/splice.c:933 [inline] direct_splice_actor+0xe4/0x1c0 fs/splice.c:1142 splice_direct_to_actor+0x2a0/0x7e4 fs/splice.c:1088 do_splice_direct+0x20c/0x348 fs/splice.c:1194 do_sendfile+0x4bc/0xc70 fs/read_write.c:1254 __do_sys_sendfile64 fs/read_write.c:1322 [inline] __se_sys_sendfile64 fs/read_write.c:1308 [inline] __arm64_sys_sendfile64+0x160/0x3b4 fs/read_write.c:1308 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595 Code: aa1803e6 aa1903e7 a90023f5 94792f6a (d4210000)

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

March 18, 2024

Last Modified

March 10, 2025

References (10)

Patch Availability(20)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1043 (5.4.0-1043.47) @ focal2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.5.0.41.41) @ mantic2026-10-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.106.106) @ jammy2026-10-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1054.52) @ jammy2026-10-24ubuntu
ubuntulinux-tools-bluefield (5.4.0.1084.80) @ focal2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04 (6.5.0.41.41~22.04.2) @ jammy2026-10-24ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.5.0.1021.29) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure (4.15.0.1183.198~14.04.1) @ trusty2026-10-24ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.24~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.231.215) @ bionic2026-10-24ubuntu
ubuntulinux-tools-oracle (4.15.0.1137.148~16.04.1) @ xenial2026-10-24ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.261.295~14.04.1) @ trusty2026-10-24ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1061.61) @ jammy2026-10-24ubuntu
ubuntulinux-tools-laptop-23.10 (6.5.0.1017.20) @ mantic2026-10-24ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1057.57) @ jammy2026-10-24ubuntu
ubuntulinux-tools-starfive (6.5.0.1015.17) @ mantic2026-10-24ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1058.64~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.26) @ mantic2026-10-24ubuntu
ubuntulinux-tools-oem-22.04d (6.5.0.1024.26) @ jammy2026-10-24ubuntu
linuxKernel @ 4.19.307 (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.209-2~deb10u1 (13 versions)
  • every version up to 5.10.216-1~deb10u1: fixed in 5.10.216-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (39 versions)
  • every version up to 5.10.216-1: fixed in 5.10.216-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (17 versions)
  • every version up to 6.1.76-1: fixed in 6.1.76-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.15-1: fixed in 6.6.15-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.15-1: fixed in 6.6.15-1
—

All Vendor Advisories

(19)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2024-26636?
CVE-2024-26636 is a medium-severity vulnerability; its CVE record was published on March 18, 2024. In the Linux kernel, the following vulnerability has been resolved: llc: make llc_ui_sendmsg() more robust against bonding changes syzbot was able to trick llc_ui_sendmsg(), allocating an skb with no headroom, but subsequently trying to push 14 bytes of Ethernet header [1] Like some others,…
When was the CVE record for CVE-2024-26636 published?
The CVE record for CVE-2024-26636 was published on March 18, 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 March 10, 2025; the record at its source may have been updated since.
Is CVE-2024-26636 actively exploited?
CVE-2024-26636 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26636?
CVE-2024-26636 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-26636?
A fix for CVE-2024-26636 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-26636

Explore →

Is Your Infrastructure Affected by CVE-2024-26636?

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

Book a Demo →Browse All CVEs