CVE-2024-26669

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2024-04-02. NVD baseline CVSS 7.1; 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-23931 (ENISA EUVD) · GHSA-2wjh-rvr2-xxjw (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
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.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net/sched: flower: Fix chain template offload

When a qdisc is deleted from a net device the stack instructs the underlying driver to remove its flow offload callback from the associated filter block using the 'FLOW_BLOCK_UNBIND' command. The stack then continues to replay the removal of the filters in the block for this driver by iterating over the chains in the block and invoking the 'reoffload' operation of the classifier being used. In turn, the classifier in its 'reoffload' operation prepares and emits a 'FLOW_CLS_DESTROY' command for each filter.

However, the stack does not do the same for chain templates and the underlying driver never receives a 'FLOW_CLS_TMPLT_DESTROY' command when a qdisc is deleted. This results in a memory leak [1] which can be reproduced using [2].

Fix by introducing a 'tmplt_reoffload' operation and have the stack invoke it with the appropriate arguments as part of the replay. Implement the operation in the sole classifier that supports chain templates (flower) by emitting the 'FLOW_CLS_TMPLT_{CREATE,DESTROY}' command based on whether a flow offload callback is being bound to a filter block or being unbound from one.

As far as I can tell, the issue happens since cited commit which reordered tcf_block_offload_unbind() before tcf_block_flush_all_chains() in __tcf_block_put(). The order cannot be reversed as the filter block is expected to be freed after flushing all the chains.

[1] unreferenced object 0xffff888107e28800 (size 2048): comm "tc", pid 1079, jiffies 4294958525 (age 3074.287s) hex dump (first 32 bytes): b1 a6 7c 11 81 88 ff ff e0 5b b3 10 81 88 ff ff ..|......[...... 01 00 00 00 00 00 00 00 e0 aa b0 84 ff ff ff ff ................ backtrace: [] __kmem_cache_alloc_node+0x1e8/0x320 [] __kmalloc+0x4e/0x90 [] mlxsw_sp_acl_ruleset_get+0x34d/0x7a0 [] mlxsw_sp_flower_tmplt_create+0x145/0x180 [] mlxsw_sp_flow_block_cb+0x1ea/0x280 [] tc_setup_cb_call+0x183/0x340 [] fl_tmplt_create+0x3da/0x4c0 [] tc_ctl_chain+0xa15/0x1170 [] rtnetlink_rcv_msg+0x3cc/0xed0 [] netlink_rcv_skb+0x170/0x440 [] netlink_unicast+0x540/0x820 [] netlink_sendmsg+0x8d8/0xda0 [] ____sys_sendmsg+0x30f/0xa80 [] ___sys_sendmsg+0x13a/0x1e0 [] __sys_sendmsg+0x11c/0x1f0 [] do_syscall_64+0x40/0xe0 unreferenced object 0xffff88816d2c0400 (size 1024): comm "tc", pid 1079, jiffies 4294958525 (age 3074.287s) hex dump (first 32 bytes): 40 00 00 00 00 00 00 00 57 f6 38 be 00 00 00 00 @.......W.8..... 10 04 2c 6d 81 88 ff ff 10 04 2c 6d 81 88 ff ff ..,m......,m.... backtrace: [] __kmem_cache_alloc_node+0x1e8/0x320 [] __kmalloc_node+0x51/0x90 [] kvmalloc_node+0xa6/0x1f0 [] bucket_table_alloc.isra.0+0x83/0x460 [] rhashtable_init+0x43b/0x7c0 [] mlxsw_sp_acl_ruleset_get+0x428/0x7a0 [] mlxsw_sp_flower_tmplt_create+0x145/0x180 [] mlxsw_sp_flow_block_cb+0x1ea/0x280 [] tc_setup_cb_call+0x183/0x340 [] fl_tmplt_create+0x3da/0x4c0 [] tc_ctl_chain+0xa15/0x1170 [] rtnetlink_rcv_msg+0x3cc/0xed0 [] netlink_rcv_skb+0x170/0x440 [] netlink_unicast+0x540/0x820 [] netlink_sendmsg+0x8d8/0xda0 [] ____sys_sendmsg+0x30f/0xa80

[2] # tc qdisc add dev swp1 clsact # tc chain add dev swp1 ingress proto ip chain 1 flower dst_ip 0.0.0.0/32 # tc qdisc del dev ---truncated---

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-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-29). 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

October 30, 2026

Advisory Details (3)

Auto-updated Oct 27, 2026
Patch available.
Web page

net/sched: flower: Fix chain template offload - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: flower: Fix chain template offload - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: flower: Fix chain template offload - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32f2a0afa95fae0d1ceec2ff06e0e816939964b8

Patch Availability(24)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-64k (6.5.0.1024.26) @ mantic2026-10-20ubuntu
ubuntulinux-tools-oem-22.04d (6.5.0.1024.26) @ jammy2026-10-20ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.5.0.1021.29) @ jammy2026-10-20ubuntu
ubuntulinux-virtual-hwe-22.04 (6.5.0.41.41~22.04.2) @ jammy2026-10-20ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.24~22.04.1) @ jammy2026-10-20ubuntu
ubuntulinux-tools-bluefield (5.4.0.1094.90) @ focal2026-10-20ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.200.196) @ focal2026-10-20ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1054 (5.4.0-1054.58) @ focal2026-10-20ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1134.143~18.04.1) @ bionic2026-10-20ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.125.135~20.04.1) @ focal2026-10-20ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1072.72) @ jammy2026-10-20ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1119.149) @ focal2026-10-20ubuntu
ubuntulinux-tools-iot (5.4.0.1044.42) @ focal2026-10-20ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1075.73) @ jammy2026-10-20ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1067.73~20.04.1) @ focal2026-10-20ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1078.87~20.04.1) @ focal2026-10-20ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.5.0.41.41.1~22.04.1) @ jammy2026-10-20ubuntu
ubuntulinux-tools-starfive (6.5.0.1015.17) @ mantic2026-10-20ubuntu
ubuntulinux-tools-laptop-23.10 (6.5.0.1017.20) @ mantic2026-10-20ubuntu
redhatkernel-0:5.14.0-427.74.1.el9_42025-06-25redhat
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
redhatkernel-rt-0:4.18.0-553.16.1.rt7.357.el8_102024-08-08redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat
linuxKernel @ 6.6.15 (fixes >=5.1.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (353 versions)
  • every version on: no fix on record
—
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
—

Weakness Classification(1)

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

Additional Vendor Advisories

(19)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2024-26669?
CVE-2024-26669 is a high-severity vulnerability; its CVE record was published on April 2, 2024. In the Linux kernel, the following vulnerability has been resolved: net/sched: flower: Fix chain template offload When a qdisc is deleted from a net device the stack instructs the underlying driver to remove its flow offload callback from the associated filter block using the 'FLOW_BLOCK_UNBIND'…
When was the CVE record for CVE-2024-26669 published?
The CVE record for CVE-2024-26669 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 October 30, 2026; the record at its source may have been updated since.
Is CVE-2024-26669 actively exploited?
CVE-2024-26669 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-26669?
CVE-2024-26669 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2024-26669?
A fix for CVE-2024-26669 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-26669 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-26669

Explore →

Is Your Infrastructure Affected by CVE-2024-26669?

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