CVE-2026-81001

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:

slip: fix use-after-free in sl_sync()

slip_devs[] stores bare net_device pointers and takes no reference on them. sl_sync() and sl_alloc() walk that table from slip_open() under rtnl_lock(), while an entry is dropped by sl_free_netdev(), which sl_setup() installs as dev->priv_destructor.

priv_destructor is called from netdev_run_todo(), which deliberately runs with the RTNL semaphore released so that it can sleep while waiting for the device refcount to drop:

/* Snapshot list, allow later requests */ list_replace_init(&net_todo_list, &list);

__rtnl_unlock(); ... if (dev->priv_destructor) dev->priv_destructor(dev); /* slip_devs[i] = NULL */ if (dev->needs_free_netdev) free_netdev(dev); ... /* Free network device */ kobject_put(&dev->dev.kobj);

So rtnl_lock() does not serialise slip_open() against the teardown at all. sl_sync() can load slip_devs[i] while the entry is still published and dereference it after netdev_run_todo() has run the destructor and released the device:

CPU0 (slip_open) CPU1 (slip_close) unregister_netdev() rtnl_unlock() netdev_run_todo() __rtnl_unlock() rtnl_lock() sl_sync() dev = slip_devs[i] priv_destructor(dev) slip_devs[i] = NULL kobject_put(&dev->dev.kobj) /* dev is freed */ sl = netdev_priv(dev) if (sl->tty || sl->leased) /* use-after-free */

BUG: KASAN: use-after-free in sl_sync drivers/net/slip/slip.c:730 [inline] BUG: KASAN: use-after-free in slip_open+0xef4/0x1210 drivers/net/slip/slip.c:806 Read of size 1 at addr ffff8880712dac71 by task syz-executor.2/6506

CPU: 2 PID: 6506 Comm: syz-executor.2 Not tainted 6.1.134-syzkaller-00260-g0c8fc3469765 #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Call Trace: sl_sync drivers/net/slip/slip.c:730 [inline] slip_open+0xef4/0x1210 drivers/net/slip/slip.c:806 tty_ldisc_open+0xa2/0x120 drivers/tty/tty_ldisc.c:433 tty_set_ldisc+0x324/0x720 drivers/tty/tty_ldisc.c:564 tiocsetd drivers/tty/tty_io.c:2428 [inline] tty_ioctl+0x5f0/0x1530 drivers/tty/tty_io.c:2712

Allocated by task 6502: alloc_netdev_mqs+0x98/0xfe0 net/core/dev.c:10719 sl_alloc drivers/net/slip/slip.c:756 [inline] slip_open+0x36d/0x1210 drivers/net/slip/slip.c:817 tty_ldisc_open+0xa2/0x120 drivers/tty/tty_ldisc.c:433 tty_set_ldisc+0x324/0x720 drivers/tty/tty_ldisc.c:564

Freed by task 6497: device_release+0xa2/0x240 drivers/base/core.c:2507 kobject_put+0x179/0x280 lib/kobject.c:729 netdev_run_todo+0x6c8/0xef0 net/core/dev.c:10509 slip_close+0x166/0x1c0 drivers/net/slip/slip.c:906 tty_ldisc_close+0x113/0x1a0 drivers/tty/tty_ldisc.c:456 tty_ldisc_kill+0x94/0x160 drivers/tty/tty_ldisc.c:614 tty_ldisc_release+0xe3/0x2b0 drivers/tty/tty_ldisc.c:782 tty_release+0xbcc/0xe70 drivers/tty/tty_io.c:1860

Commit e58c19124189 ("slip: Fix use-after-free Read in slip_open") fixed a different source of stale entries - a device left in slip_devs[] after slip_open() freed it on the registration error path - and does not address this race, which is why the report survives it.

Drop the entry from ndo_uninit instead. unregister_netdevice() calls ndo_uninit under RTNL, before the device is queued to netdev_run_todo(), so an entry that sl_sync() can still see while holding RTNL belongs to a device that cannot be freed until RTNL is dropped. sl_free_netdev() stays only for the slip_open() error path, where register_netdevice() may have failed before ndo_init and ndo_uninit is then not called either. Both running for the same device is harmless: the ---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
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

September 11, 2026

Last Modified

September 14, 2026

Advisory Details (4)

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

slip: fix use-after-free in sl_sync() - kernel/git/stable/linux.git - Linux kernel stable tree

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

slip: fix use-after-free in sl_sync() - kernel/git/stable/linux.git - Linux kernel stable tree

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

slip: fix use-after-free in sl_sync() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/486577db807891d0f964fdf13c1640c7f54b0ad1
Web page

slip: fix use-after-free in sl_sync() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c4e7c42d77e78ad595dbb9e4b5886b58b45d89d

Vendor Advisories for CVE-2026-81001(1)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-81001?
CVE-2026-81001 is a high-severity vulnerability; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: slip: fix use-after-free in sl_sync() slipdevs[] stores bare netdevice pointers and takes no reference on them. slsync() and slalloc() walk that table from slip_open() under rtnllock(), while an entry is dropped by slfree_netdev(),…
When was the CVE record for CVE-2026-81001 published?
The CVE record for CVE-2026-81001 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 14, 2026; the record at its source may have been updated since.
Is CVE-2026-81001 actively exploited?
CVE-2026-81001 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-81001?
CVE-2026-81001 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-81001?
A fix for CVE-2026-81001 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-81001 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-81001

Explore →

Is Your Infrastructure Affected by CVE-2026-81001?

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

Book a Demo →Browse All CVEs