CVE-2026-72354

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-08-15. 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 — 3 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.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ntfs: avoid stale runlist element dereference in MFT writeback

ntfs_write_mft_block() maps each $MFT record through the $MFT data runlist. For sub-folio clusters it looks up a struct runlist_element under ni->runlist.lock, drops the lock, and later uses rl->length and rl->vcn when choosing folio_sz.

That pointer is only borrowed from ni->runlist.rl. Concurrent $MFT allocation extension can merge a replacement runlist under the same lock, and ntfs_rl_realloc() can free the old backing array. If that happens between the lookup and the later folio_sz decision, writeback can dereference freed runlist storage.

The buggy scenario involves two paths, with each column showing the order within that path:

MFT writeback path: $MFT allocation extension:

  • Look up rl under 1. Extend the $MFT data allocation.
ni->runlist.lock. 2. Publish a replacement runlist.
  • Drop ni->runlist.lock. 3. Free the old runlist array.
  • Read rl->length and rl->vcn
to choose folio_sz.

Compute the remaining run length while ni->runlist.lock is still held, and use that scalar after unlock. This preserves the existing folio sizing decision without carrying a borrowed runlist_element across the lock boundary.

Validation reproduced this kernel report: BUG: KASAN: slab-use-after-free in ntfs_mft_writepages+0x1c8d/0x1fb0

Call Trace: dump_stack_lvl+0x66/0xa0 print_report+0xce/0x630 ? ntfs_mft_writepages+0x1c8d/0x1fb0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __virt_addr_valid+0x20d/0x410 ? ntfs_mft_writepages+0x1c8d/0x1fb0 kasan_report+0xe0/0x110 ? ntfs_mft_writepages+0x1c8d/0x1fb0 ntfs_mft_writepages+0x1c8d/0x1fb0 ? __pfx_ntfs_mft_writepages+0x10/0x10 ? __pfx___mutex_unlock_slowpath+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? iput+0x92/0xa80 do_writepages+0x219/0x530 ? __pfx_do_writepages+0x10/0x10 __writeback_single_inode+0x117/0xf50 ? do_raw_spin_lock+0x130/0x270 ? __pfx_do_raw_spin_lock+0x10/0x10 ? __pfx___writeback_single_inode+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 writeback_sb_inodes+0x65b/0x1810 ? srso_alias_return_thunk+0x5/0xfbef5 ? lock_acquire+0x2b8/0x2f0 ? __pfx_writeback_sb_inodes+0x10/0x10 ? lock_release+0x1e0/0x280 ? _raw_spin_unlock+0x23/0x40 ? move_expired_inodes+0x2b8/0x850 __writeback_inodes_wb+0xf4/0x270 ? __pfx___writeback_inodes_wb+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? queue_io+0x2e4/0x410 wb_writeback+0x666/0x880 ? srso_alias_return_thunk+0x5/0xfbef5 ? __pfx_wb_writeback+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? get_nr_dirty_inodes+0x1c/0x170 wb_workfn+0x75e/0xbb0 ? srso_alias_return_thunk+0x5/0xfbef5 ? _raw_spin_unlock_irqrestore+0x27/0x60 ? __pfx_wb_workfn+0x10/0x10 ? __pfx_debug_object_deactivate+0x10/0x10 ? lock_acquire+0x2b8/0x2f0 ? srso_alias_return_thunk+0x5/0xfbef5 ? lock_release+0x1e0/0x280 process_one_work+0x8d0/0x1870 ? __pfx_process_one_work+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 worker_thread+0x575/0xf80 ? __pfx_worker_thread+0x10/0x10 kthread+0x2e7/0x3c0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x576/0x810 ? __pfx_ret_from_fork+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? __switch_to+0x57e/0xe10 ? __switch_to_asm+0x33/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30

Allocated by task 970: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 __kvmalloc_node_noprof+0x353/0x920 ntfs_rl_realloc+0x3c/0x80 ntfs_runlists_merge+0x1212/0x3010 ntfs_mft_data_extend_allocation_nolock+0x3e0/0x1f40 ntfs_mft_record_alloc+0x1ab4/0x4f10 __ntfs_create+0x680/0x2e50 ntfs_create+0x1e6/0x3a0 path_openat+0x2b55/0x3c10 do_file_open+0x1f4/0x460 do_sys_openat2+0xde/0x170 __x64_sys_openat+0x122/0x1e0 do_syscall_64+0x115/0x6a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 1294: kasan_save_ ---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 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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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.5%
EPSS %ILE
42nd
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). 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

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
Patch available.
Web page

ntfs: avoid stale runlist element dereference in MFT writeback - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs: avoid stale runlist element dereference in MFT writeback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/81fe702ff1760da32bcd3ef4494b2a33dbeced72

Vendor Advisories for CVE-2026-72354(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-72354?
CVE-2026-72354 is a high-severity vulnerability; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ntfs: avoid stale runlist element dereference in MFT writeback ntfswritemft_block() maps each $MFT record through the $MFT data runlist. For sub-folio clusters it looks up a struct runlist_element under ni->runlist.lock, drops the…
When was the CVE record for CVE-2026-72354 published?
The CVE record for CVE-2026-72354 was published on August 15, 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 August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-72354 actively exploited?
CVE-2026-72354 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72354?
CVE-2026-72354 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-72354?
A fix for CVE-2026-72354 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72354 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-72354

Explore →

Is Your Infrastructure Affected by CVE-2026-72354?

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

Book a Demo →Browse All CVEs