CVE-2024-26907

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-04-17. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-24169 (ENISA EUVD) · GHSA-vh2f-wj96-fxxh (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

RDMA/mlx5: Fix fortify source warning while accessing Eth segment

------------[ cut here ]------------ memcpy: detected field-spanning write (size 56) of single field "eseg->inline_hdr.start" at /var/lib/dkms/mlnx-ofed-kernel/5.8/build/drivers/infiniband/hw/mlx5/wr.c:131 (size 2) WARNING: CPU: 0 PID: 293779 at /var/lib/dkms/mlnx-ofed-kernel/5.8/build/drivers/infiniband/hw/mlx5/wr.c:131 mlx5_ib_post_send+0x191b/0x1a60 [mlx5_ib] Modules linked in: 8021q garp mrp stp llc rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) ib_uverbs(OE) ib_core(OE) mlx5_core(OE) pci_hyperv_intf mlxdevm(OE) mlx_compat(OE) tls mlxfw(OE) psample nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables libcrc32c nfnetlink mst_pciconf(OE) knem(OE) vfio_pci vfio_pci_core vfio_iommu_type1 vfio iommufd irqbypass cuse nfsv3 nfs fscache netfs xfrm_user xfrm_algo ipmi_devintf ipmi_msghandler binfmt_misc crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha512_ssse3 snd_pcsp aesni_intel crypto_simd cryptd snd_pcm snd_timer joydev snd soundcore input_leds serio_raw evbug nfsd auth_rpcgss nfs_acl lockd grace sch_fq_codel sunrpc drm efi_pstore ip_tables x_tables autofs4 psmouse virtio_net net_failover failover floppy [last unloaded: mlx_compat(OE)] CPU: 0 PID: 293779 Comm: ssh Tainted: G OE 6.2.0-32-generic #32~22.04.1-Ubuntu Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 RIP: 0010:mlx5_ib_post_send+0x191b/0x1a60 [mlx5_ib] Code: 0c 01 00 a8 01 75 25 48 8b 75 a0 b9 02 00 00 00 48 c7 c2 10 5b fd c0 48 c7 c7 80 5b fd c0 c6 05 57 0c 03 00 01 e8 95 4d 93 da <0f> 0b 44 8b 4d b0 4c 8b 45 c8 48 8b 4d c0 e9 49 fb ff ff 41 0f b7 RSP: 0018:ffffb5b48478b570 EFLAGS: 00010046 RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffb5b48478b628 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffb5b48478b5e8 R13: ffff963a3c609b5e R14: ffff9639c3fbd800 R15: ffffb5b480475a80 FS: 00007fc03b444c80(0000) GS:ffff963a3dc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000556f46bdf000 CR3: 0000000006ac6003 CR4: 00000000003706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ? show_regs+0x72/0x90 ? mlx5_ib_post_send+0x191b/0x1a60 [mlx5_ib] ? __warn+0x8d/0x160 ? mlx5_ib_post_send+0x191b/0x1a60 [mlx5_ib] ? report_bug+0x1bb/0x1d0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x19/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? mlx5_ib_post_send+0x191b/0x1a60 [mlx5_ib] mlx5_ib_post_send_nodrain+0xb/0x20 [mlx5_ib] ipoib_send+0x2ec/0x770 [ib_ipoib] ipoib_start_xmit+0x5a0/0x770 [ib_ipoib] dev_hard_start_xmit+0x8e/0x1e0 ? validate_xmit_skb_list+0x4d/0x80 sch_direct_xmit+0x116/0x3a0 __dev_xmit_skb+0x1fd/0x580 __dev_queue_xmit+0x284/0x6b0 ? _raw_spin_unlock_irq+0xe/0x50 ? __flush_work.isra.0+0x20d/0x370 ? push_pseudo_header+0x17/0x40 [ib_ipoib] neigh_connected_output+0xcd/0x110 ip_finish_output2+0x179/0x480 ? __smp_call_single_queue+0x61/0xa0 __ip_finish_output+0xc3/0x190 ip_finish_output+0x2e/0xf0 ip_output+0x78/0x110 ? __pfx_ip_finish_output+0x10/0x10 ip_local_out+0x64/0x70 __ip_queue_xmit+0x18a/0x460 ip_queue_xmit+0x15/0x30 __tcp_transmit_skb+0x914/0x9c0 tcp_write_xmit+0x334/0x8d0 tcp_push_one+0x3c/0x60 tcp_sendmsg_locked+0x2e1/0xac0 tcp_sendmsg+0x2d/0x50 inet_sendmsg+0x43/0x90 sock_sendmsg+0x68/0x80 sock_write_iter+0x93/0x100 vfs_write+0x326/0x3c0 ksys_write+0xbd/0xf0 ? do_syscall_64+0x69/0x90 __x64_sys_write+0x19/0x30 do_syscall_ ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
18th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 17, 2024

Last Modified

October 15, 2026

Advisory Details (6)

Auto-updated May 12, 2026
Patch available.
Web page

RDMA/mlx5: Fix fortify source warning while accessing Eth segment - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a624a5f95733bac4648ecadb320ca83aa9c08fd
Web page

RDMA/mlx5: Fix fortify source warning while accessing Eth segment - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60ba938a8bc8c90e724c75f98e932f9fb7ae1b9d
Web page

RDMA/mlx5: Fix fortify source warning while accessing Eth segment - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d5e86a56615cc387d21c629f9af8fb0e958d350
Web page

RDMA/mlx5: Fix fortify source warning while accessing Eth segment - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/185fa07000e0a81d54cf8c05414cebff14469a5c
Web page

RDMA/mlx5: Fix fortify source warning while accessing Eth segment - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d27c48dc309da72c3b46351a1205d89687272baa
Web page

RDMA/mlx5: Fix fortify source warning while accessing Eth segment - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cad82f1671e41094acd3b9a60cd27d67a3c64a21

Patch Availability(19)

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.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.82-1 (19 versions)
  • every version up to 6.1.85-1: fixed in 6.1.85-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

(14)

Data Freshness Timeline

(refreshed 10× in last 7d / 47× 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 98 of 228 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-26907?
CVE-2024-26907 is a high-severity vulnerability; its CVE record was published on April 17, 2024. In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix fortify source warning while accessing Eth segment ------------[ cut here ]------------ memcpy: detected field-spanning write (size 56) of single field "eseg->inline_hdr.start" at…
When was the CVE record for CVE-2024-26907 published?
The CVE record for CVE-2024-26907 was published on April 17, 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-26907 actively exploited?
CVE-2024-26907 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26907?
CVE-2024-26907 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-26907?
A fix for CVE-2024-26907 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-26907 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-26907

Explore →

Is Your Infrastructure Affected by CVE-2024-26907?

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