CVE-2026-64434

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
8.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: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref

l2cap_chan_timeout() runs asynchronously and accesses chan->conn. If the connection is torn down while the timer is running or pending, chan->conn can be freed, leading to a use-after-free when the timer worker attempts to lock conn->lock:

| BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | BUG: KASAN: slab-use-after-free in atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | BUG: KASAN: slab-use-after-free in __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | BUG: KASAN: slab-use-after-free in mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | Write of size 8 at addr ffff8881298d9550 by task kworker/2:1/83 | | CPU: 2 UID: 0 PID: 83 Comm: kworker/2:1 Not tainted 7.1.0-rc6-next-20260601-dirty #6 PREEMPT(full) | Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 | Workqueue: events l2cap_chan_timeout | Call Trace: | | instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | l2cap_chan_timeout+0x5d/0x1b0 net/bluetooth/l2cap_core.c:422 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | | | Allocated by task 320: | l2cap_conn_add+0xa7/0x820 net/bluetooth/l2cap_core.c:7075 | l2cap_connect_cfm+0xdb/0xd70 net/bluetooth/l2cap_core.c:7452 | hci_connect_cfm include/net/bluetooth/hci_core.h:2139 [inline] | hci_remote_features_evt+0x52f/0x9f0 net/bluetooth/hci_event.c:3760 | hci_event_func net/bluetooth/hci_event.c:7796 [inline] | hci_event_packet+0x561/0xa70 net/bluetooth/hci_event.c:7847 | hci_rx_work+0x370/0x890 net/bluetooth/hci_core.c:4040 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | | Freed by task 322: | hci_disconn_cfm include/net/bluetooth/hci_core.h:2154 [inline] | hci_conn_hash_flush+0x101/0x1f0 net/bluetooth/hci_conn.c:2736 | hci_dev_close_sync+0x889/0xde0 net/bluetooth/hci_sync.c:5405 | hci_dev_do_close net/bluetooth/hci_core.c:502 [inline] | hci_unregister_dev+0x1f7/0x370 net/bluetooth/hci_core.c:2679 | vhci_release+0x12a/0x180 drivers/bluetooth/hci_vhci.c:690 | __fput+0x369/0x890 fs/file_table.c:510 | task_work_run+0x160/0x1d0 kernel/task_work.c:233 | get_signal+0xf5b/0x1120 kernel/signal.c:2810 | arch_do_signal_or_restart+0x4d/0x600 arch/x86/kernel/signal.c:337 | __exit_to_user_mode_loop kernel/entry/common.c:64 [inline] | exit_to_user_mode_loop+0x85/0x510 kernel/entry/common.c:98 | do_syscall_64+0x263/0x3d0 arch/x86/entry/syscall_64.c:100 | entry_SYSCALL_64_after_hwframe+0x77/0x7f | | The buggy address belongs to the object at ffff8881298d9400 | which belongs to the cache kmalloc-512 of size 512 | The buggy address is located 336 bytes inside of | freed 512-byte region [ffff8881298d9400, ffff8881298d9600)

Fix it by having chan->conn hold a reference to l2cap_conn (via l2cap_conn_get) when the channel is added to the connection, and releasing it in the channel destructor. This ensures the l2cap_conn remains alive as long as the channel exists.

A new FLAG_DEL channel flag is introduced to indicate that the ch ---truncated---

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
15th
KEV
Not listed

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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

July 25, 2026

Last Modified

September 3, 2026

Advisory Details (5)

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

Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50c38d9f42a529691e4e67ea9cedf4f0bfc8d277
Web page

Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b0e2bf39cf99e458d991b9df253727e036a7d7d
Web page

Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91047a4396a8b1857a6f712a90cf33ec0012b189

Vendor Advisories for CVE-2026-64434(2)

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

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-10-07ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-10-07ubuntu
ubuntulinux-tools-ibm-7.0 (7.0.0-1013.13) @ resolute2026-10-07ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2018.18) @ resolute2026-10-07ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18) @ resolute2026-10-07ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1011.11) @ resolute2026-10-07ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-10-07ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-10-07ubuntu

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:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.12—
  • every version up to 6.12.100-1~deb12u1: fixed in 6.12.100-1~deb12u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (159 versions)
  • every version up to 7.1.4-1: fixed in 7.1.4-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(8)

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 15× in last 7d / 80× 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 100 of 331 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. None are among the latest 100 rows. The 231 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64434?
CVE-2026-64434 is a high-severity vulnerability; its CVE record was published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref l2capchantimeout() runs asynchronously and accesses chan->conn. If the connection is torn down while the timer is running or pending, chan->conn can be freed, leading…
When was the CVE record for CVE-2026-64434 published?
The CVE record for CVE-2026-64434 was published on July 25, 2026. 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 September 3, 2026; the record at its source may have been updated since.
Is CVE-2026-64434 actively exploited?
CVE-2026-64434 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64434?
CVE-2026-64434 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64434?
A fix for CVE-2026-64434 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64434 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-2026-64434

Explore →

Is Your Infrastructure Affected by CVE-2026-64434?

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

Book a Demo →Browse All CVEs