CVE-2026-64065

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 2026-07-19. 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-2026-45638 (ENISA EUVD) · GHSA-23r9-pmc9-fcx4 (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.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

netfs: fix VM_BUG_ON_FOLIO() issue in netfs_write_begin() call

The multiple runs of generic/013 test-case is capable to reproduce a kernel BUG at mm/filemap.c:1504 with probability of 30%.

while true; do sudo ./check generic/013 done

[ 9849.452376] page: refcount:3 mapcount:0 mapping:00000000e58ff252 index:0x10781 pfn:0x1c322 [ 9849.452412] memcg:ffff8881a1915800 [ 9849.452417] aops:ceph_aops ino:1000058db9e dentry name(?):"f9XXXXXX" [ 9849.452432] flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff) [ 9849.452441] raw: 0017ffffc0000000 0000000000000000 dead000000000122 ffff88816110d248 [ 9849.452445] raw: 0000000000010781 0000000000000000 00000003ffffffff ffff8881a1915800 [ 9849.452447] page dumped because: VM_BUG_ON_FOLIO(!folio_test_locked(folio)) [ 9849.452474] ------------[ cut here ]------------ [ 9849.452476] kernel BUG at mm/filemap.c:1504! [ 9849.478635] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI [ 9849.481772] CPU: 2 UID: 0 PID: 84223 Comm: fsstress Not tainted 7.0.0-rc1+ #18 PREEMPT(full) [ 9849.482881] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-9.fc43 06/1 0/2025 [ 9849.484539] RIP: 0010:folio_unlock+0x85/0xa0 [ 9849.485076] Code: 89 df 31 f6 e8 1c f3 ff ff 48 8b 5d f8 c9 31 c0 31 d2 31 f6 31 ff c3 cc cc cc cc 48 c7 c6 80 6c d9 a7 48 89 df e8 4b b3 10 00 <0f> 0b 48 89 df e8 21 e6 2c 00 eb 9d 0f 1f 40 00 66 66 2e 0f 1f 84 [ 9849.493818] RSP: 0018:ffff8881bb8076b0 EFLAGS: 00010246 [ 9849.495740] RAX: 0000000000000000 RBX: ffffea00070c8980 RCX: 0000000000000000 [ 9849.498678] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 9849.500559] RBP: ffff8881bb8076b8 R08: 0000000000000000 R09: 0000000000000000 [ 9849.501097] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000010782000 [ 9849.502108] R13: ffff8881935de738 R14: ffff88816110d010 R15: 0000000000001000 [ 9849.502516] FS: 00007e36cbe94740(0000) GS:ffff88824a899000(0000) knlGS:0000000000000000 [ 9849.502996] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 9849.503810] CR2: 000000c0002b0000 CR3: 000000011bbf6004 CR4: 0000000000772ef0 [ 9849.504459] PKRU: 55555554 [ 9849.504626] Call Trace: [ 9849.505242] [ 9849.505379] netfs_write_begin+0x7c8/0x10a0 [ 9849.505877] ? __kasan_check_read+0x11/0x20 [ 9849.506384] ? __pfx_netfs_write_begin+0x10/0x10 [ 9849.507178] ceph_write_begin+0x8c/0x1c0 [ 9849.507934] generic_perform_write+0x391/0x8f0 [ 9849.508503] ? __pfx_generic_perform_write+0x10/0x10 [ 9849.509062] ? file_update_time_flags+0x19a/0x4b0 [ 9849.509581] ? ceph_get_caps+0x63/0xf0 [ 9849.510259] ? ceph_get_caps+0x63/0xf0 [ 9849.510530] ceph_write_iter+0xe79/0x1ae0 [ 9849.511282] ? __pfx_ceph_write_iter+0x10/0x10 [ 9849.511839] ? lock_acquire+0x1ad/0x310 [ 9849.512334] ? ksys_write+0xf9/0x230 [ 9849.512582] ? lock_is_held_type+0xaa/0x140 [ 9849.513128] vfs_write+0x512/0x1110 [ 9849.513634] ? __fget_files+0x33/0x350 [ 9849.513893] ? __pfx_vfs_write+0x10/0x10 [ 9849.514143] ? mutex_lock_nested+0x1b/0x30 [ 9849.514394] ksys_write+0xf9/0x230 [ 9849.514621] ? __pfx_ksys_write+0x10/0x10 [ 9849.514887] ? do_syscall_64+0x25e/0x1520 [ 9849.515122] ? __kasan_check_read+0x11/0x20 [ 9849.515366] ? trace_hardirqs_on_prepare+0x178/0x1c0 [ 9849.515655] __x64_sys_write+0x72/0xd0 [ 9849.515885] ? trace_hardirqs_on+0x24/0x1c0 [ 9849.516130] x64_sys_call+0x22f/0x2390 [ 9849.516341] do_syscall_64+0x12b/0x1520 [ 9849.516545] ? do_syscall_64+0x27c/0x1520 [ 9849.516783] ? do_syscall_64+0x27c/0x1520 [ 9849.517003] ? lock_release+0x318/0x480 [ 9849.517220] ? __x64_sys_io_getevents+0x143/0x2d0 [ 9849.517479] ? percpu_ref_put_many.constprop.0+0x8f/0x210 [ 9849.517779] ? entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 9849.518073] ? do_syscall_64+0x25e/0x1520 [ 9849.518291] ? __kasan_check_read+0x11/0x20 [ 9849.518519] ? trace_hardirqs_on_prepare+0x178/0x1c0 [ 9849.518799] ? do_syscall_64+0x27c/0x1520 [ 9 ---truncated---

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.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

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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 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 19, 2026

Last Modified

September 3, 2026

Advisory Details (4)

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

netfs: fix VM_BUG_ON_FOLIO() issue in netfs_write_begin() call - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfs: fix VM_BUG_ON_FOLIO() issue in netfs_write_begin() call - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfs: fix VM_BUG_ON_FOLIO() issue in netfs_write_begin() call - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ad05b6f5df296ef046589f222bb2587495b991e
Web page

netfs: fix VM_BUG_ON_FOLIO() issue in netfs_write_begin() call - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51ffb788f074c0a61953086f49008028c1e7b645

Vendor Advisories for CVE-2026-64065(1)

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

Patch Availability(8)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)
  • every version up to 7.0.12-1: fixed in 7.0.12-1
—

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 8× in last 7d / 42× 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 170 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 70 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-64065?
CVE-2026-64065 is a medium-severity vulnerability; its CVE record was published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: netfs: fix VMBUGONFOLIO() issue in netfswrite_begin() call The multiple runs of generic/013 test-case is capable to reproduce a kernel BUG at mm/filemap.c:1504 with probability of 30%. while true; do sudo ./check generic/013 done […
When was the CVE record for CVE-2026-64065 published?
The CVE record for CVE-2026-64065 was published on July 19, 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-64065 actively exploited?
CVE-2026-64065 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-64065?
CVE-2026-64065 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64065?
A fix for CVE-2026-64065 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64065 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-64065

Explore →

Is Your Infrastructure Affected by CVE-2026-64065?

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