CVE-2026-64453

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 2026-07-25. 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 — 3 sources updated this week
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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

usb: misc: usbio: fix disconnect UAF in client teardown

usbio_disconnect() walks usbio->cli_list in reverse and uninitializes each auxiliary device. auxiliary_device_uninit() drops the device reference, and for an unbound child that can run usbio_auxdev_release() and free the containing struct usbio_client.

list_for_each_entry_reverse() advances after the loop body by reading client->link.prev. If the current client is freed by auxiliary_device_uninit(), the iterator dereferences freed memory.

Use list_for_each_entry_safe_reverse() so the previous client is cached before the body can drop the final reference. This preserves reverse teardown order while keeping the next iterator cursor independent of the current client's lifetime.

Validation reproduced this kernel report: BUG: KASAN: slab-use-after-free in usbio_disconnect+0x12e/0x150

Call Trace: dump_stack_lvl+0x66/0xa0 print_report+0xce/0x630 ? usbio_disconnect+0x12e/0x150 ? srso_alias_return_thunk+0x5/0xfbef5 ? __virt_addr_valid+0x188/0x320 ? usbio_disconnect+0x12e/0x150 kasan_report+0xe0/0x110 ? usbio_disconnect+0x12e/0x150 usbio_disconnect+0x12e/0x150 usb_unbind_interface+0xf3/0x400 really_probe+0x316/0x660 __driver_probe_device+0x106/0x240 driver_probe_device+0x4a/0x110 __device_attach_driver+0xf1/0x1a0 ? __pfx___device_attach_driver+0x10/0x10 bus_for_each_drv+0xf9/0x160 ? __pfx_bus_for_each_drv+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? trace_hardirqs_on+0x18/0x130 ? srso_alias_return_thunk+0x5/0xfbef5 ? _raw_spin_unlock_irqrestore+0x44/0x60 __device_attach+0x133/0x2a0 ? __pfx___device_attach+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? do_raw_spin_unlock+0x9a/0x100 ? srso_alias_return_thunk+0x5/0xfbef5 device_initial_probe+0x55/0x70 bus_probe_device+0x4a/0xd0 device_add+0x9b9/0xc10 ? __pfx_device_add+0x10/0x10 ? _raw_spin_unlock_irqrestore+0x44/0x60 ? srso_alias_return_thunk+0x5/0xfbef5 ? lockdep_hardirqs_on_prepare+0xea/0x1a0 ? srso_alias_return_thunk+0x5/0xfbef5 ? usb_enable_lpm+0x3c/0x260 usb_set_configuration+0xb64/0xf20 usb_generic_driver_probe+0x5f/0x90 usb_probe_device+0x71/0x1b0 really_probe+0x46b/0x660 __driver_probe_device+0x106/0x240 driver_probe_device+0x4a/0x110 __device_attach_driver+0xf1/0x1a0 ? __pfx___device_attach_driver+0x10/0x10 bus_for_each_drv+0xf9/0x160 ? __pfx_bus_for_each_drv+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? trace_hardirqs_on+0x18/0x130 ? srso_alias_return_thunk+0x5/0xfbef5 ? _raw_spin_unlock_irqrestore+0x44/0x60 __device_attach+0x133/0x2a0 ? __pfx___device_attach+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? do_raw_spin_unlock+0x9a/0x100 ? srso_alias_return_thunk+0x5/0xfbef5 device_initial_probe+0x55/0x70 bus_probe_device+0x4a/0xd0 device_add+0x9b9/0xc10 ? __pfx_device_add+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? add_device_randomness+0xb7/0xf0 usb_new_device+0x492/0x870 hub_event+0x1b10/0x29c0 ? __pfx_hub_event+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? lock_acquire+0x187/0x300 ? process_one_work+0x475/0xb90 ? srso_alias_return_thunk+0x5/0xfbef5 ? lock_release+0xc8/0x290 ? srso_alias_return_thunk+0x5/0xfbef5 process_one_work+0x4d7/0xb90 ? __pfx_process_one_work+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? __list_add_valid_or_report+0x37/0xf0 ? __pfx_hub_event+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 worker_thread+0x2d8/0x570 ? __pfx_worker_thread+0x10/0x10 kthread+0x1ad/0x1f0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x3c9/0x540 ? __pfx_ret_from_fork+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? __switch_to+0x2e9/0x730 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30

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 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)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.2% × 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.2%
EPSS %ILE
5th
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 (3)

Auto-updated Sep 3, 2026
Patch available.
Web page

usb: misc: usbio: fix disconnect UAF in client teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: misc: usbio: fix disconnect UAF in client teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1947b6411460d68b54b13c536961933166937d05
Web page

usb: misc: usbio: fix disconnect UAF in client teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0bfeec21984fedd32987f4e4c0cde34b445af404

Vendor Advisories for CVE-2026-64453(1)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-07ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-10-07ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2018.18) @ resolute2026-10-07ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1011.11) @ resolute2026-10-07ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-07ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18) @ resolute2026-10-07ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-31.31~24.04.1) @ noble2026-10-07ubuntu
ubuntulinux-tools-ibm-7.0 (7.0.0-1013.13) @ resolute2026-10-07ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-10-07ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-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

(1 across 1 ecosystem)
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.

All Vendor Advisories

(11)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64453?
CVE-2026-64453 is a high-severity vulnerability; its CVE record was published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: misc: usbio: fix disconnect UAF in client teardown usbiodisconnect() walks usbio->clilist in reverse and uninitializes each auxiliary device. auxiliarydeviceuninit() drops the device reference, and for an unbound child that…
When was the CVE record for CVE-2026-64453 published?
The CVE record for CVE-2026-64453 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-64453 actively exploited?
CVE-2026-64453 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64453?
CVE-2026-64453 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64453?
A fix for CVE-2026-64453 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64453 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-64453

Explore →

Is Your Infrastructure Affected by CVE-2026-64453?

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

Book a Demo →Browse All CVEs