CVE-2026-45898

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-27. A secondary CVSS source baseline 9.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

Also known asEUVD-2026-32364 (ENISA EUVD) · GHSA-527m-87rr-p4rj (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

RDMA/iwcm: Fix workqueue list corruption by removing work_list

The commit e1168f0 ("RDMA/iwcm: Simplify cm_event_handler()") changed the work submission logic to unconditionally call queue_work() with the expectation that queue_work() would have no effect if work was already pending. The problem is that a free list of struct iwcm_work is used (for which struct work_struct is embedded), so each call to queue_work() is basically unique and therefore does indeed queue the work.

This causes a problem in the work handler which walks the work_list until it's empty to process entries. This means that a single run of the work handler could process item N+1 and release it back to the free list while the actual workqueue entry is still queued. It could then get reused (INIT_WORK...) and lead to list corruption in the workqueue logic.

Fix this by just removing the work_list. The workqueue already does this for us.

This fixes the following error that was observed when stress testing with ucmatose on an Intel E830 in iWARP mode:

[ 151.465780] list_del corruption. next->prev should be ffff9f0915c69c08, but was ffff9f0a1116be08. (next=ffff9f0a15b11c08) [ 151.466639] ------------[ cut here ]------------ [ 151.466986] kernel BUG at lib/list_debug.c:67! [ 151.467349] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 151.467753] CPU: 14 UID: 0 PID: 2306 Comm: kworker/u64:18 Not tainted 6.19.0-rc4+ #1 PREEMPT(voluntary) [ 151.468466] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 151.469192] Workqueue: 0x0 (iw_cm_wq) [ 151.469478] RIP: 0010:__list_del_entry_valid_or_report+0xf0/0x100 [ 151.469942] Code: c7 58 5f 4c b2 e8 10 50 aa ff 0f 0b 48 89 ef e8 36 57 cb ff 48 8b 55 08 48 89 e9 48 89 de 48 c7 c7 a8 5f 4c b2 e8 f0 4f aa ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 90 90 90 90 90 90 [ 151.471323] RSP: 0000:ffffb15644e7bd68 EFLAGS: 00010046 [ 151.471712] RAX: 000000000000006d RBX: ffff9f0915c69c08 RCX: 0000000000000027 [ 151.472243] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9f0a37d9c600 [ 151.472768] RBP: ffff9f0a15b11c08 R08: 0000000000000000 R09: c0000000ffff7fff [ 151.473294] R10: 0000000000000001 R11: ffffb15644e7bba8 R12: ffff9f092339ee68 [ 151.473817] R13: ffff9f0900059c28 R14: ffff9f092339ee78 R15: 0000000000000000 [ 151.474344] FS: 0000000000000000(0000) GS:ffff9f0a847b5000(0000) knlGS:0000000000000000 [ 151.474934] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 151.475362] CR2: 0000559e233a9088 CR3: 000000020296b004 CR4: 0000000000770ef0 [ 151.475895] PKRU: 55555554 [ 151.476118] Call Trace: [ 151.476331] [ 151.476497] move_linked_works+0x49/0xa0 [ 151.476792] __pwq_activate_work.isra.46+0x2f/0xa0 [ 151.477151] pwq_dec_nr_in_flight+0x1e0/0x2f0 [ 151.477479] process_scheduled_works+0x1c8/0x410 [ 151.477823] worker_thread+0x125/0x260 [ 151.478108] ? __pfx_worker_thread+0x10/0x10 [ 151.478430] kthread+0xfe/0x240 [ 151.478671] ? __pfx_kthread+0x10/0x10 [ 151.478955] ? __pfx_kthread+0x10/0x10 [ 151.479240] ret_from_fork+0x208/0x270 [ 151.479523] ? __pfx_kthread+0x10/0x10 [ 151.479806] ret_from_fork_asm+0x1a/0x30 [ 151.480103]

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-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-30). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

May 27, 2026

Last Modified

October 19, 2026

Advisory Details (10)

Auto-updated Oct 27, 2026
Patch available. Sources: redhat.
Red HatMentions a patch (unverified)

2482031 – (CVE-2026-45898) CVE-2026-45898 kernel: RDMA/iwcm: Fix workqueue list corruption by removing work_list

Affected: Red Hat Enterprise Linux 10.0 Extended Update Support

https://bugzilla.redhat.com/show_bug.cgi?id=2482031
Red HatMentions a patch (unverified)

CVE-2026-45898 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-45898
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:30848
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:30129
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.0 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:27731
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.6 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:27708
Web page

RDMA/iwcm: Fix workqueue list corruption by removing work_list - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/iwcm: Fix workqueue list corruption by removing work_list - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/iwcm: Fix workqueue list corruption by removing work_list - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7874eeacfa42177565c01d5198726671acf7adf2
Web page

RDMA/iwcm: Fix workqueue list corruption by removing work_list - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/38c5b49fffa1b760959af74f11806eeb3ef4706d

Vendor Advisories for CVE-2026-45898(5)

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04 (6.17.0-40.40~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1026.26) @ noble2026-10-28ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-10-28ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1021.21) @ questing2026-10-28ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-40.40) @ questing2026-10-28ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1017.19) @ questing2026-10-28ubuntu
redhatkernel-0:5.14.0-687.19.1.el9_82026-06-29redhat
redhatkernel-0:6.12.0-211.28.1.el10_22026-06-25redhat
redhatkernel-0:5.14.0-570.123.1.el9_62026-06-22redhat
redhatkernel-0:6.12.0-55.82.1.el10_02026-06-22redhat
linuxKernel @ 6.12.75 (fixes >=6.11.0)—osv

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.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (104 versions)
  • every version up to 6.18.14-1: fixed in 6.18.14-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(8)

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 26× in last 7d / 95× 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 573 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 473 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45898?
CVE-2026-45898 is a critical-severity vulnerability; its CVE record was published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix workqueue list corruption by removing work_list The commit e1168f0 ("RDMA/iwcm: Simplify cmeventhandler()") changed the work submission logic to unconditionally call queuework() with the expectation that queuework()…
When was the CVE record for CVE-2026-45898 published?
The CVE record for CVE-2026-45898 was published on May 27, 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 19, 2026; the record at its source may have been updated since.
Is CVE-2026-45898 actively exploited?
CVE-2026-45898 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45898?
CVE-2026-45898 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45898?
A fix for CVE-2026-45898 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45898 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-45898

Explore →

Is Your Infrastructure Affected by CVE-2026-45898?

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

Book a Demo →Browse All CVEs