CVE-2024-26656

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-04-02. 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-23918 (ENISA EUVD) · GHSA-cmxf-xmv7-xjq8 (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:

drm/amdgpu: fix use-after-free bug

The bug can be triggered by sending a single amdgpu_gem_userptr_ioctl to the AMDGPU DRM driver on any ASICs with an invalid address and size. The bug was reported by Joonkyo Jung . For example the following code:

static void Syzkaller1(int fd) { struct drm_amdgpu_gem_userptr arg; int ret;

arg.addr = 0xffffffffffff0000; arg.size = 0x80000000; /*2 Gb*/ arg.flags = 0x7; ret = drmIoctl(fd, 0xc1186451/*amdgpu_gem_userptr_ioctl*/, &arg); }

Due to the address and size are not valid there is a failure in amdgpu_hmm_register->mmu_interval_notifier_insert->__mmu_interval_notifier_insert-> check_shl_overflow, but we even the amdgpu_hmm_register failure we still call amdgpu_hmm_unregister into amdgpu_gem_object_free which causes access to a bad address. The following stack is below when the issue is reproduced when Kazan is enabled:

[ +0.000014] Hardware name: ASUS System Product Name/ROG STRIX B550-F GAMING (WI-FI), BIOS 1401 12/03/2020 [ +0.000009] RIP: 0010:mmu_interval_notifier_remove+0x327/0x340 [ +0.000017] Code: ff ff 49 89 44 24 08 48 b8 00 01 00 00 00 00 ad de 4c 89 f7 49 89 47 40 48 83 c0 22 49 89 47 48 e8 ce d1 2d 01 e9 32 ff ff ff <0f> 0b e9 16 ff ff ff 4c 89 ef e8 fa 14 b3 ff e9 36 ff ff ff e8 80 [ +0.000014] RSP: 0018:ffffc90002657988 EFLAGS: 00010246 [ +0.000013] RAX: 0000000000000000 RBX: 1ffff920004caf35 RCX: ffffffff8160565b [ +0.000011] RDX: dffffc0000000000 RSI: 0000000000000004 RDI: ffff8881a9f78260 [ +0.000010] RBP: ffffc90002657a70 R08: 0000000000000001 R09: fffff520004caf25 [ +0.000010] R10: 0000000000000003 R11: ffffffff8161d1d6 R12: ffff88810e988c00 [ +0.000010] R13: ffff888126fb5a00 R14: ffff88810e988c0c R15: ffff8881a9f78260 [ +0.000011] FS: 00007ff9ec848540(0000) GS:ffff8883cc880000(0000) knlGS:0000000000000000 [ +0.000012] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ +0.000010] CR2: 000055b3f7e14328 CR3: 00000001b5770000 CR4: 0000000000350ef0 [ +0.000010] Call Trace: [ +0.000006] [ +0.000007] ? show_regs+0x6a/0x80 [ +0.000018] ? __warn+0xa5/0x1b0 [ +0.000019] ? mmu_interval_notifier_remove+0x327/0x340 [ +0.000018] ? report_bug+0x24a/0x290 [ +0.000022] ? handle_bug+0x46/0x90 [ +0.000015] ? exc_invalid_op+0x19/0x50 [ +0.000016] ? asm_exc_invalid_op+0x1b/0x20 [ +0.000017] ? kasan_save_stack+0x26/0x50 [ +0.000017] ? mmu_interval_notifier_remove+0x23b/0x340 [ +0.000019] ? mmu_interval_notifier_remove+0x327/0x340 [ +0.000019] ? mmu_interval_notifier_remove+0x23b/0x340 [ +0.000020] ? __pfx_mmu_interval_notifier_remove+0x10/0x10 [ +0.000017] ? kasan_save_alloc_info+0x1e/0x30 [ +0.000018] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? __kasan_kmalloc+0xb1/0xc0 [ +0.000018] ? srso_return_thunk+0x5/0x5f [ +0.000013] ? __kasan_check_read+0x11/0x20 [ +0.000020] amdgpu_hmm_unregister+0x34/0x50 [amdgpu] [ +0.004695] amdgpu_gem_object_free+0x66/0xa0 [amdgpu] [ +0.004534] ? __pfx_amdgpu_gem_object_free+0x10/0x10 [amdgpu] [ +0.004291] ? do_syscall_64+0x5f/0xe0 [ +0.000023] ? srso_return_thunk+0x5/0x5f [ +0.000017] drm_gem_object_free+0x3b/0x50 [drm] [ +0.000489] amdgpu_gem_userptr_ioctl+0x306/0x500 [amdgpu] [ +0.004295] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004270] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? __this_cpu_preempt_check+0x13/0x20 [ +0.000015] ? srso_return_thunk+0x5/0x5f [ +0.000013] ? sysvec_apic_timer_interrupt+0x57/0xc0 [ +0.000020] ? srso_return_thunk+0x5/0x5f [ +0.000014] ? asm_sysvec_apic_timer_interrupt+0x1b/0x20 [ +0.000022] ? drm_ioctl_kernel+0x17b/0x1f0 [drm] [ +0.000496] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004272] ? drm_ioctl_kernel+0x190/0x1f0 [drm] [ +0.000492] drm_ioctl_kernel+0x140/0x1f0 [drm] [ +0.000497] ? __pfx_amdgpu_gem_userptr_ioctl+0x10/0x10 [amdgpu] [ +0.004297] ? __pfx_drm_ioctl_kernel+0x10/0x10 [d ---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.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.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

April 2, 2024

Last Modified

August 5, 2026

References (5)

Vendor Advisories for CVE-2024-26656(9)

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

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-64k (6.8.0-1006.6) @ noble2026-10-24ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1006.6+1) @ noble2026-10-24ubuntu
ubuntulinux-tools-gcp (6.8.0-1008.9) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-35.35) @ noble2026-10-24ubuntu
ubuntulinux-tools-gke (6.8.0-1004.7) @ noble2026-10-24ubuntu
redhatkernel-0:4.18.0-372.129.1.el8_62024-11-13redhat
redhatkernel-0:5.14.0-427.44.1.el9_42024-11-13redhat
redhatkernel-rt-0:5.14.0-284.92.1.rt14.377.el9_22024-11-13redhat
redhatkernel-0:5.14.0-284.92.1.el9_22024-11-13redhat
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
redhatkernel-0:4.18.0-477.64.1.el8_82024-07-23redhat
redhatkernel-rt-0:4.18.0-553.8.1.rt7.349.el8_102024-07-08redhat
redhatkernel-0:4.18.0-553.8.1.el8_102024-07-02redhat
linuxKernel @ 6.1.132 (fixes >=4.2.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 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
linux-6.16.1.106-3~deb11u1 ... 6.1.129-1~deb11u1 (7 versions)
  • every version up to 6.1.137-1~deb11u1: fixed in 6.1.137-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (36 versions)
  • every version up to 6.1.133-1: fixed in 6.1.133-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

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 97 of 213 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 116 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:31 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:29 UTCEPSS rescoreEPSS 0.2% · 14th 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% · 13th percentile
  11. 2026-10-24 08:25 UTCEG score recompute
  12. 2026-10-24 08:25 UTCVendor advisory
  13. 2026-10-24 08:25 UTCGHSA enrichmentGHSA-cmxf-xmv7-xjq8 · GitHub CVSS 5.5
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-10-19 20:25 UTCOSV refresh
  19. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  21. 2026-10-18 07:23 UTCEG score recompute
  22. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
Show 72 more
  1. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-10-12 17:59 UTCEG score recompute
  3. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-10-11 21:24 UTCEG score recompute
  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% · 12th percentile
  20. 2026-09-27 01:12 UTCOSV refresh
  21. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  22. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  24. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  26. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  27. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  28. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  30. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  31. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  32. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  33. 2026-09-07 10:48 UTCOSV refresh
  34. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  35. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  36. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  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-27 14:23 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  47. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  48. 2026-08-20 19:31 UTCOSV refresh
  49. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  50. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  51. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  52. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  53. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  54. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  55. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  56. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  57. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  58. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  59. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  60. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  61. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  62. 2026-08-05 12:24 UTCEG score recompute
  63. 2026-08-05 12:24 UTCVendor advisory
  64. 2026-08-05 12:24 UTCGHSA enrichmentGHSA-cmxf-xmv7-xjq8 · GitHub CVSS 5.5
  65. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  66. 2026-08-04 12:20 UTCEG score recompute
  67. 2026-08-04 12:20 UTCVendor advisory
  68. 2026-08-04 12:20 UTCGHSA enrichmentGHSA-cmxf-xmv7-xjq8 · GitHub CVSS 5.5
  69. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  70. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  71. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  72. 2026-08-01 08:36 UTCOSV refresh

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-26656?
CVE-2024-26656 is a medium-severity vulnerability; its CVE record was published on April 2, 2024. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix use-after-free bug The bug can be triggered by sending a single amdgpu_gem_userptr_ioctl to the AMDGPU DRM driver on any ASICs with an invalid address and size. The bug was reported by Joonkyo Jung…
When was the CVE record for CVE-2024-26656 published?
The CVE record for CVE-2024-26656 was published on April 2, 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-26656 actively exploited?
CVE-2024-26656 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-26656?
CVE-2024-26656 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-26656?
A fix for CVE-2024-26656 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-26656 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-26656

Explore →

Is Your Infrastructure Affected by CVE-2024-26656?

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

Book a Demo →Browse All CVEs