CVE-2026-74289

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-08-15. 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 — 4 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.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ipv4: fib: Don't dump dying fib_info in fib_leaf_notify().

syzbot reported use-after-free in nsim_fib4_prepare_event(). [0]

The problem is that the following functions call fib_info_hold() / refcount_inc() while dumping fib_info under RCU, which is unsafe.

* mlxsw_sp_router_fib4_event() * rocker_router_fib_event() * nsim_fib4_prepare_event()

refcount_inc_not_zero() must be used, but it would be too late there.

Let's guarantee the lifetime of fib_info in fib_leaf_notify().

Note that IPv6 does not need the corresponding change since fib6_table_dump() holds fib6_table.tb6_lock.

[0]: refcount_t: addition on 0; use-after-free. WARNING: lib/refcount.c:25 at refcount_warn_saturate+0x9f/0x110 lib/refcount.c:25, CPU#0: kworker/u8:15/3420 Modules linked in: CPU: 0 UID: 0 PID: 3420 Comm: kworker/u8:15 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 Workqueue: netns cleanup_net RIP: 0010:refcount_warn_saturate+0x9f/0x110 lib/refcount.c:25 Code: eb 66 85 db 74 3e 83 fb 01 75 4c e8 1b f1 22 fd 48 8d 3d 84 cb f1 0a 67 48 0f b9 3a eb 4a e8 08 f1 22 fd 48 8d 3d 81 cb f1 0a <67> 48 0f b9 3a eb 37 e8 f5 f0 22 fd 48 8d 3d 7e cb f1 0a 67 48 0f RSP: 0018:ffffc9000f2c7270 EFLAGS: 00010293 RAX: ffffffff84a18858 RBX: 0000000000000002 RCX: ffff888032ff9ec0 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8f9353e0 RBP: 0000000000000000 R08: ffff888032ff9ec0 R09: 0000000000000005 R10: 0000000000000100 R11: 0000000000000004 R12: ffff8880570cc000 R13: dffffc0000000000 R14: ffff88802b40563c R15: ffff8880570cc000 FS: 0000000000000000(0000) GS:ffff888126173000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fb1f4d5d000 CR3: 000000006072a000 CR4: 00000000003526f0 Call Trace: __refcount_add include/linux/refcount.h:-1 [inline] __refcount_inc include/linux/refcount.h:366 [inline] refcount_inc include/linux/refcount.h:383 [inline] fib_info_hold include/net/ip_fib.h:629 [inline] nsim_fib4_prepare_event drivers/net/netdevsim/fib.c:930 [inline] nsim_fib_event_schedule_work drivers/net/netdevsim/fib.c:1000 [inline] nsim_fib_event_nb+0x1055/0x1240 drivers/net/netdevsim/fib.c:1043 call_fib_notifier+0x45/0x80 net/core/fib_notifier.c:25 call_fib_entry_notifier net/ipv4/fib_trie.c:90 [inline] fib_leaf_notify net/ipv4/fib_trie.c:2176 [inline] fib_table_notify net/ipv4/fib_trie.c:2194 [inline] fib_notify+0x36b/0x5e0 net/ipv4/fib_trie.c:2217 fib_net_dump net/core/fib_notifier.c:70 [inline] register_fib_notifier+0x184/0x360 net/core/fib_notifier.c:108 nsim_fib_create+0x85d/0x9f0 drivers/net/netdevsim/fib.c:1596 nsim_dev_reload_create drivers/net/netdevsim/dev.c:1604 [inline] nsim_dev_reload_up+0x374/0x7c0 drivers/net/netdevsim/dev.c:1058 devlink_reload+0x501/0x8d0 net/devlink/dev.c:475 devlink_pernet_pre_exit+0x1ff/0x420 net/devlink/core.c:558 ops_pre_exit_list net/core/net_namespace.c:161 [inline] ops_undo_list+0x187/0x940 net/core/net_namespace.c:234 cleanup_net+0x56e/0x800 net/core/net_namespace.c:702 process_one_work kernel/workqueue.c:3314 [inline] process_scheduled_works+0xb5d/0x1860 kernel/workqueue.c:3397 worker_thread+0xa53/0xfc0 kernel/workqueue.c:3478 kthread+0x388/0x470 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

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 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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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.1%
EPSS %ILE
2nd
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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 Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

October 16, 2026

Advisory Details (2)

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

ipv4: fib: Don't dump dying fib_info in fib_leaf_notify(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/676482da8d938ea72c26da0fc86af2d2ec238ab2
Web page

ipv4: fib: Don't dump dying fib_info in fib_leaf_notify(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06b693d2eb6651a63ad85bad8673de3b7d4edd6d

Vendor Advisories for CVE-2026-74289(2)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-10-16ubuntu
ubuntulinux-tools-aws-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-16ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-16ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1036.39) @ noble2026-10-16ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-16ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-16ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-38.38~24.04.4) @ noble2026-10-16ubuntu

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

(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.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74289?
CVE-2026-74289 is a high-severity vulnerability; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv4: fib: Don't dump dying fibinfo in fibleaf_notify(). syzbot reported use-after-free in nsimfib4prepare_event(). [0] The problem is that the following functions call fibinfohold() / refcountinc() while dumping fibinfo under RCU,…
When was the CVE record for CVE-2026-74289 published?
The CVE record for CVE-2026-74289 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 October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-74289 actively exploited?
CVE-2026-74289 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74289?
CVE-2026-74289 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-74289?
A fix for CVE-2026-74289 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74289 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-74289

Explore →

Is Your Infrastructure Affected by CVE-2026-74289?

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

Book a Demo →Browse All CVEs