CVE-2024-50095

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-11-05. 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-44570 (ENISA EUVD) · GHSA-935g-fc8j-74rf (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.7%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

RDMA/mad: Improve handling of timed out WRs of mad agent

Current timeout handler of mad agent acquires/releases mad_agent_priv lock for every timed out WRs. This causes heavy locking contention when higher no. of WRs are to be handled inside timeout handler.

This leads to softlockup with below trace in some use cases where rdma-cm path is used to establish connection between peer nodes

Trace: ----- BUG: soft lockup - CPU#4 stuck for 26s! [kworker/u128:3:19767] CPU: 4 PID: 19767 Comm: kworker/u128:3 Kdump: loaded Tainted: G OE ------- --- 5.14.0-427.13.1.el9_4.x86_64 #1 Hardware name: Dell Inc. PowerEdge R740/01YM03, BIOS 2.4.8 11/26/2019 Workqueue: ib_mad1 timeout_sends [ib_core] RIP: 0010:__do_softirq+0x78/0x2ac RSP: 0018:ffffb253449e4f98 EFLAGS: 00000246 RAX: 00000000ffffffff RBX: 0000000000000000 RCX: 000000000000001f RDX: 000000000000001d RSI: 000000003d1879ab RDI: fff363b66fd3a86b RBP: ffffb253604cbcd8 R08: 0000009065635f3b R09: 0000000000000000 R10: 0000000000000040 R11: ffffb253449e4ff8 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000040 FS: 0000000000000000(0000) GS:ffff8caa1fc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fd9ec9db900 CR3: 0000000891934006 CR4: 00000000007706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: ? show_trace_log_lvl+0x1c4/0x2df ? show_trace_log_lvl+0x1c4/0x2df ? __irq_exit_rcu+0xa1/0xc0 ? watchdog_timer_fn+0x1b2/0x210 ? __pfx_watchdog_timer_fn+0x10/0x10 ? __hrtimer_run_queues+0x127/0x2c0 ? hrtimer_interrupt+0xfc/0x210 ? __sysvec_apic_timer_interrupt+0x5c/0x110 ? sysvec_apic_timer_interrupt+0x37/0x90 ? asm_sysvec_apic_timer_interrupt+0x16/0x20 ? __do_softirq+0x78/0x2ac ? __do_softirq+0x60/0x2ac __irq_exit_rcu+0xa1/0xc0 sysvec_call_function_single+0x72/0x90 asm_sysvec_call_function_single+0x16/0x20 RIP: 0010:_raw_spin_unlock_irq+0x14/0x30 RSP: 0018:ffffb253604cbd88 EFLAGS: 00000247 RAX: 000000000001960d RBX: 0000000000000002 RCX: ffff8cad2a064800 RDX: 000000008020001b RSI: 0000000000000001 RDI: ffff8cad5d39f66c RBP: ffff8cad5d39f600 R08: 0000000000000001 R09: 0000000000000000 R10: ffff8caa443e0c00 R11: ffffb253604cbcd8 R12: ffff8cacb8682538 R13: 0000000000000005 R14: ffffb253604cbd90 R15: ffff8cad5d39f66c cm_process_send_error+0x122/0x1d0 [ib_cm] timeout_sends+0x1dd/0x270 [ib_core] process_one_work+0x1e2/0x3b0 ? __pfx_worker_thread+0x10/0x10 worker_thread+0x50/0x3a0 ? __pfx_worker_thread+0x10/0x10 kthread+0xdd/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x29/0x50

Simplified timeout handler by creating local list of timed out WRs and invoke send handler post creating the list. The new method acquires/ releases lock once to fetch the list and hence helps to reduce locking contetiong when processing higher no. of WRs

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.7% × 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.7%
EPSS %ILE
54th
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.7% 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

November 5, 2024

Last Modified

October 15, 2026

References (10)

Vendor Advisories for CVE-2024-50095(1)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-15ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-15ubuntu
ubuntulinux-tools-fips (4.15.0.1142.139) @ bionic2026-10-15ubuntu
ubuntulinux-tools-fips (4.4.0.1120.121) @ xenial2026-10-15ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.276.282) @ xenial2026-10-15ubuntu
ubuntulinux-tools-gcp-fips-5.4 (5.4.0.1156.98) @ focal2026-10-15ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1136.167) @ focal2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1071 (5.4.0-1071.75) @ focal2026-10-15ubuntu
ubuntulinux-tools-gcp-fips-4.15 (4.15.0.2088.86) @ bionic2026-10-15ubuntu
ubuntulinux-tools-azure (4.15.0.1195.210~14.04.1) @ trusty2026-10-15ubuntu
ubuntulinux-tools-azure-fips-4.15 (4.15.0.2104.100) @ bionic2026-10-15ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1156.163~18.04.1) @ bionic2026-10-15ubuntu
ubuntulinux-tools-azure-fips-5.4 (5.4.0.1157.94) @ focal2026-10-15ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1151.161~18.04.1) @ bionic2026-10-15ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1078.76) @ jammy2026-10-15ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-15ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.127.137~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1073.79~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1078.87~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1039.43) @ jammy2026-10-15ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.127.126) @ jammy2026-10-15ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1071.71) @ jammy2026-10-15ubuntu
ubuntulinux-virtual (6.8.0-56.58) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1025.30) @ noble2026-10-15ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1022.22) @ noble2026-10-15ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1024.24) @ noble2026-10-15ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1018.19) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-57.59~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-10-15ubuntu
linuxKernel @ 5.10.227 (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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)
  • every version up to 5.10.234-1: fixed in 5.10.234-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1
  • every version up to 6.1.119-1~deb11u1: fixed in 6.1.119-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (30 versions)
  • every version up to 6.1.115-1: fixed in 6.1.115-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.4-1: fixed in 6.11.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.4-1: fixed in 6.11.4-1
—

Additional Vendor Advisories

(24)

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2024-50095?
CVE-2024-50095 is a medium-severity vulnerability; its CVE record was published on November 5, 2024. In the Linux kernel, the following vulnerability has been resolved: RDMA/mad: Improve handling of timed out WRs of mad agent Current timeout handler of mad agent acquires/releases mad_agent_priv lock for every timed out WRs. This causes heavy locking contention when higher no. of WRs are to be…
When was the CVE record for CVE-2024-50095 published?
The CVE record for CVE-2024-50095 was published on November 5, 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-50095 actively exploited?
CVE-2024-50095 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-50095?
CVE-2024-50095 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-50095?
A fix for CVE-2024-50095 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-50095 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-50095

Explore →

Is Your Infrastructure Affected by CVE-2024-50095?

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

Book a Demo →Browse All CVEs