CVE-2026-89754

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-11. A secondary CVSS source baseline 7.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
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:

mm/pagewalk: fix stale walk->action escaping walk_pmd_range()

If ->pmd_entry() sets walk->action = ACTION_AGAIN, the pmd_none() check is retried. The PMD entry may be cleared at the point of retry.

In this case, if walk->ops->install_pte is not specified, the code continues to the next PMD entry in the range without resetting walk->action to ACTION_SUBTREE.

This leaves walk->action erroneously set to ACTION_AGAIN, which is incorrect.

This was incorrect but not problematic up until commit 3b89863c3fa4 ("mm/pagewalk: fix race between concurrent split and refault") which updated walk_pud_range() to check for walk->action == ACTION_AGAIN upon walk_pmd_range()'s return, causing the PUD walk to be retried.

In this case this results in duplicate walk callbacks being invoked, which is erroneous and will break any caller that is not idempotent with respect to this (and waste time for those which are). The result is an out-of-bounds write, triggered by a local fuzzer:

[ 2.272695] ================================================================== [ 2.273471] BUG: KASAN: slab-out-of-bounds in __mincore_unmapped_range+0x14f/0x190 [ 2.274302] Write of size 1 at addr ffff888008d9b000 by task poc/106 [ 2.274966] [ 2.275154] CPU: 0 UID: 1000 PID: 106 Comm: poc Not tainted 7.2.0-rc6-00429-ga7c7074b58d2 #55 PREEMPT(lazy) [ 2.275159] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 2.275164] Call Trace: [ 2.275170] [ 2.275172] dump_stack_lvl+0x53/0x70 [ 2.275200] print_report+0xd0/0x630 [ 2.275210] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 2.275219] ? irqentry_exit+0xd2/0x670 [ 2.275224] ? irqentry_exit+0xd2/0x670 [ 2.275226] ? __virt_addr_valid+0xef/0x1a0 [ 2.275239] ? __mincore_unmapped_range+0x14f/0x190 [ 2.275242] kasan_report+0xce/0x100 [ 2.275245] ? __mincore_unmapped_range+0x14f/0x190 [ 2.275248] __mincore_unmapped_range+0x14f/0x190 [ 2.275252] mincore_unmapped_range+0x45/0x70 [ 2.275254] walk_pgd_range+0xafc/0xfc0 [ 2.275261] ? __pfx_walk_pgd_range+0x10/0x10 [ 2.275264] ? __update_load_avg_se+0x3d1/0x670 [ 2.275275] __walk_page_range+0xc0/0x310 [ 2.275278] ? __pfx_find_vma+0x10/0x10 [ 2.275281] ? finish_task_switch.isra.0+0x16d/0x4f0 [ 2.275290] walk_page_range_mm_unsafe+0x26f/0x3a0 [ 2.275293] ? __pfx_mtree_load+0x10/0x10 [ 2.275298] ? __pfx_walk_page_range_mm_unsafe+0x10/0x10 [ 2.275302] ? __free_frozen_pages+0x54d/0x7e0 [ 2.275308] __do_sys_mincore+0x132/0x380 [ 2.275311] do_syscall_64+0xf9/0x540 [ 2.275316] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 2.275322] RIP: 0033:0x422ccd [ 2.275326] Code: b3 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 [ 2.275329] RSP: 002b:00007fffffffec18 EFLAGS: 00000287 ORIG_RAX: 000000000000001b [ 2.275337] RAX: ffffffffffffffda RBX: 0000000000000066 RCX: 0000000000422ccd [ 2.275339] RDX: 00000000004d0940 RSI: 0000000001000000 RDI: 00007ffff4000000 [ 2.275340] RBP: 00000000004d0940 R08: 0000000000000100 R09: 0000000000000100 [ 2.275342] R10: 0000000000000100 R11: 0000000000000287 R12: 20c49ba5e353f7cf [ 2.275343] R13: 00000000004990d3 R14: 0000000000000000 R15: 0000000000000001 [ 2.275346] [ 2.275347] [ 2.296904] The buggy address belongs to the object at ffff888008d9b000 [ 2.296904] which belongs to the cache sigqueue of size 80 [ 2.298151] The buggy address is located 0 bytes inside of [ 2.298151] allocated 80-byte region [ffff888008d9b000, ffff888008d9b050) [ 2.299408] [ 2.299601] The buggy address belongs to the physical page: [ 2.300191] page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8d9b ---truncated---

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
6th
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

September 11, 2026

Last Modified

September 13, 2026

Advisory Details (3)

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

mm/pagewalk: fix stale walk->action escaping walk_pmd_range() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/pagewalk: fix stale walk->action escaping walk_pmd_range() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/pagewalk: fix stale walk->action escaping walk_pmd_range() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/895cd4ecbb2e03d7583103c65ee5adaae126ed6d

Vendor Advisories for CVE-2026-89754(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.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 25× in last 7d / 111× 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 99 of 124 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 25 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-89754?
CVE-2026-89754 is a high-severity vulnerability; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/pagewalk: fix stale walk->action escaping walkpmdrange() If ->pmdentry() sets walk->action = ACTIONAGAIN, the pmd_none() check is retried. The PMD entry may be cleared at the point of retry. In this case, if…
When was the CVE record for CVE-2026-89754 published?
The CVE record for CVE-2026-89754 was published on September 11, 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 13, 2026; the record at its source may have been updated since.
Is CVE-2026-89754 actively exploited?
CVE-2026-89754 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89754?
CVE-2026-89754 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89754?
A fix for CVE-2026-89754 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89754 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-89754

Explore →

Is Your Infrastructure Affected by CVE-2026-89754?

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

Book a Demo →Browse All CVEs