CVE-2024-26931

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-05-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, 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.4%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

scsi: qla2xxx: Fix command flush on cable pull

System crash due to command failed to flush back to SCSI layer.

BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 27 PID: 793455 Comm: kworker/u130:6 Kdump: loaded Tainted: G OE --------- - - 4.18.0-372.9.1.el8.x86_64 #1 Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 09/03/2021 Workqueue: nvme-wq nvme_fc_connect_ctrl_work [nvme_fc] RIP: 0010:__wake_up_common+0x4c/0x190 Code: 24 10 4d 85 c9 74 0a 41 f6 01 04 0f 85 9d 00 00 00 48 8b 43 08 48 83 c3 08 4c 8d 48 e8 49 8d 41 18 48 39 c3 0f 84 f0 00 00 00 <49> 8b 41 18 89 54 24 08 31 ed 4c 8d 70 e8 45 8b 29 41 f6 c5 04 75 RSP: 0018:ffff95f3e0cb7cd0 EFLAGS: 00010086 RAX: 0000000000000000 RBX: ffff8b08d3b26328 RCX: 0000000000000000 RDX: 0000000000000001 RSI: 0000000000000003 RDI: ffff8b08d3b26320 RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffffffffffe8 R10: 0000000000000000 R11: ffff95f3e0cb7a60 R12: ffff95f3e0cb7d20 R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8b2fdf6c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000002f1e410002 CR4: 00000000007706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: __wake_up_common_lock+0x7c/0xc0 qla_nvme_ls_req+0x355/0x4c0 [qla2xxx] qla2xxx [0000:12:00.1]-f084:3: qlt_free_session_done: se_sess 0000000000000000 / sess ffff8ae1407ca000 from port 21:32:00:02:ac:07:ee:b8 loop_id 0x02 s_id 01:02:00 logout 1 keep 0 els_logo 0 ? __nvme_fc_send_ls_req+0x260/0x380 [nvme_fc] qla2xxx [0000:12:00.1]-207d:3: FCPort 21:32:00:02:ac:07:ee:b8 state transitioned from ONLINE to LOST - portid=010200. ? nvme_fc_send_ls_req.constprop.42+0x1a/0x45 [nvme_fc] qla2xxx [0000:12:00.1]-2109:3: qla2x00_schedule_rport_del 21320002ac07eeb8. rport ffff8ae598122000 roles 1 ? nvme_fc_connect_ctrl_work.cold.63+0x1e3/0xa7d [nvme_fc] qla2xxx [0000:12:00.1]-f084:3: qlt_free_session_done: se_sess 0000000000000000 / sess ffff8ae14801e000 from port 21:32:01:02:ad:f7:ee:b8 loop_id 0x04 s_id 01:02:01 logout 1 keep 0 els_logo 0 ? __switch_to+0x10c/0x450 ? process_one_work+0x1a7/0x360 qla2xxx [0000:12:00.1]-207d:3: FCPort 21:32:01:02:ad:f7:ee:b8 state transitioned from ONLINE to LOST - portid=010201. ? worker_thread+0x1ce/0x390 ? create_worker+0x1a0/0x1a0 qla2xxx [0000:12:00.1]-2109:3: qla2x00_schedule_rport_del 21320102adf7eeb8. rport ffff8ae3b2312800 roles 70 ? kthread+0x10a/0x120 qla2xxx [0000:12:00.1]-2112:3: qla_nvme_unregister_remote_port: unregister remoteport on ffff8ae14801e000 21320102adf7eeb8 ? set_kthread_struct+0x40/0x40 qla2xxx [0000:12:00.1]-2110:3: remoteport_delete of ffff8ae14801e000 21320102adf7eeb8 completed. ? ret_from_fork+0x1f/0x40 qla2xxx [0000:12:00.1]-f086:3: qlt_free_session_done: waiting for sess ffff8ae14801e000 logout

The system was under memory stress where driver was not able to allocate an SRB to carry out error recovery of cable pull. The failure to flush causes upper layer to start modifying scsi_cmnd. When the system frees up some memory, the subsequent cable pull trigger another command flush. At this point the driver access a null pointer when attempting to DMA unmap the SGL.

Add a check to make sure commands are flush back on session tear down to prevent the null pointer access.

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.4% × 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.4%
EPSS %ILE
29th
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.4% 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 1, 2024

Last Modified

August 5, 2026

References (9)

Vendor Advisories for CVE-2024-26931(5)

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-virtual-hwe-18.04-edge (5.4.0.189.187) @ focal2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1006.6) @ noble2026-05-24ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1112.142) @ focal2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1047 (5.4.0-1047.51) @ focal2026-05-24ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1065.65) @ jammy2026-05-24ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.116.106) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.189.209~18.04.1) @ bionic2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.116.116) @ jammy2026-05-24ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1065.71~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-iot (5.4.0.1040.38) @ focal2026-05-24ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1068.66) @ jammy2026-05-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1058.56) @ jammy2026-05-24ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1065.73~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-gke (6.8.0-1004.7) @ noble2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-05-24ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1006.6+1) @ noble2026-05-24ubuntu
ubuntulinux-tools-gcp (6.8.0-1008.9) @ noble2026-05-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-35.35) @ noble2026-05-24ubuntu
redhatkernel-0:5.14.0-427.37.1.el9_42024-09-24redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat
redhatkernel-0:5.14.0-284.75.1.el9_22024-07-24redhat
redhatkernel-rt-0:5.14.0-284.75.1.rt14.360.el9_22024-07-24redhat
linuxKernel @ 4.19.312 (fixes >=4.11.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.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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-26931?
CVE-2024-26931 is a medium-severity vulnerability; its CVE record was published on May 1, 2024. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix command flush on cable pull System crash due to command failed to flush back to SCSI layer. BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 27…
When was the CVE record for CVE-2024-26931 published?
The CVE record for CVE-2024-26931 was published on May 1, 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-26931 actively exploited?
CVE-2024-26931 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26931?
CVE-2024-26931 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-26931?
A fix for CVE-2024-26931 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-26931 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-26931

Explore →

Is Your Infrastructure Affected by CVE-2024-26931?

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

Book a Demo →Browse All CVEs