CVE-2026-89533

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-09-11. 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 — 3 sources updated this week
9.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: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

svcrdma: Fix offset arithmetic in read_chunk_range

svc_rdma_read_chunk_range() walks a Read chunk's segment list to build a sub-range starting at byte offset and spanning length bytes for a Position-Zero or Call chunk. Two arithmetic defects in the per-segment loop produce wrong DMA lengths and a u32 underflow:

pcl_for_each_segment(segment, chunk) { if (offset > segment->rs_length) { offset -= segment->rs_length; continue; }

dummy.rs_handle = segment->rs_handle; dummy.rs_length = min_t(u32, length, segment->rs_length) - offset; dummy.rs_offset = segment->rs_offset + offset;

First, the skip predicate uses '>' instead of '>='. When offset equals the segment's full rs_length, the segment is fully consumed and should be skipped, but the loop falls through into the body. The resulting dummy.rs_length is min_t(u32, length, rs_length) - rs_length, which underflows to a near-UINT_MAX u32 when length is smaller than rs_length, or is zero otherwise.

Second, the length formula subtracts offset from the min_t() result rather than from segment->rs_length before the cap. For offset > 0 the segment's residual is rs_length - offset, not rs_length, so the cap must be applied to the residual. With the current bracketing, whenever length is smaller than rs_length - offset the per-segment length becomes length - offset instead of length, silently dropping offset bytes from the rebuilt chunk. Combined with the boundary case above it also enables the u32 underflow path, which propagates a huge nr_bvec into svc_rdma_build_read_segment() and a multi-MiB kmalloc_array_node() in svc_rdma_get_rw_ctxt().

Additionally, svc_rdma_read_call_chunk() can invoke this function with length == 0 when the last Read chunk ends exactly at the end of the Call chunk. With the corrected >= predicate, every segment is skipped and the function returns the initial -EINVAL, rejecting a valid request. Return success immediately when length is zero. Also break out of the loop once length is fully consumed to avoid passing zero-length segments to svc_rdma_build_read_segment().

Fix by using '>=' so a fully-consumed segment is skipped, by moving '- offset' inside min_t() so the cap is applied to the segment's residual length, by returning success for zero-length requests, and by stopping iteration when the requested range has been consumed.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
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
41st
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 (7)

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

svcrdma: Fix offset arithmetic in read_chunk_range - kernel/git/stable/linux.git - Linux kernel stable tree

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

svcrdma: Fix offset arithmetic in read_chunk_range - kernel/git/stable/linux.git - Linux kernel stable tree

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

svcrdma: Fix offset arithmetic in read_chunk_range - kernel/git/stable/linux.git - Linux kernel stable tree

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

svcrdma: Fix offset arithmetic in read_chunk_range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ee4dc7476b3abc92ec1d444533a559f33f59561
Web page

svcrdma: Fix offset arithmetic in read_chunk_range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a44c140cc2f3643a39e258bb0c0ab9d0f494f5e
Web page

svcrdma: Fix offset arithmetic in read_chunk_range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4493c96bbd0068fadf69cbae8d13426202e34cdc
Web page

svcrdma: Fix offset arithmetic in read_chunk_range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10873311f91db9454e2fadbf9866bc819e0646d9

Vendor Advisories for CVE-2026-89533(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 41× in last 7d / 212× 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 98 of 230 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 132 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.5% · 41st percentile
  2. 2026-10-13 09:19 UTCEG score recompute
  3. 2026-10-13 09:18 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-12 14:48 UTCEG score recompute
  6. 2026-10-12 09:07 UTCEG score recompute
  7. 2026-10-12 09:06 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-11 21:10 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-11 19:15 UTCEG score recompute
  10. 2026-10-11 16:32 UTCEG score recompute
  11. 2026-10-11 15:48 UTCEG score recompute
  12. 2026-10-11 15:48 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-11 13:47 UTCEG score recompute
  15. 2026-10-11 11:41 UTCEG score recompute
  16. 2026-10-11 11:40 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-11 06:52 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-10 20:29 UTCEG score recompute
  19. 2026-10-10 20:29 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-10-10 16:20 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-10 12:06 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-10 07:58 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-10 03:32 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-09 23:24 UTCEG score recompute
Show 73 more
  1. 2026-10-09 23:24 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-09 19:16 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-09 07:37 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-09 03:27 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-08 23:20 UTCEG score recompute
  7. 2026-10-08 23:20 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-08 12:35 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-08 08:09 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-08 04:01 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-07 23:53 UTCEG score recompute
  13. 2026-10-07 23:53 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-07 19:44 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-07 12:56 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-07 08:30 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-07 04:21 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-07 00:14 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-06 20:06 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-06 15:47 UTCEG score recompute
  22. 2026-10-06 15:47 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-06 11:18 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-06 07:10 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-06 02:20 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-05 22:01 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-05 17:52 UTCEG score recompute
  29. 2026-10-05 17:52 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-10-05 13:44 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-05 09:27 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-05 05:19 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-05 01:11 UTCEG score recompute
  35. 2026-10-05 01:11 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  37. 2026-10-04 20:48 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-04 16:41 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-04 12:33 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-04 08:26 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-04 04:17 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-04 00:09 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-03 19:09 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-03 15:01 UTCEG score recompute
  45. 2026-10-03 15:01 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-03 10:50 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-03 06:42 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-03 02:34 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-02 22:26 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-02 18:18 UTCEG score recompute
  51. 2026-10-02 18:18 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-02 14:01 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-02 09:54 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-02 05:46 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-02 00:21 UTCEG score recompute
  56. 2026-10-02 00:21 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  58. 2026-10-01 19:27 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-01 15:06 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-10-01 10:59 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-01 06:51 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-10-01 02:41 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-09-30 22:34 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-30 18:20 UTCEG score recompute
  65. 2026-09-30 18:19 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  67. 2026-09-30 14:09 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-09-30 10:01 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-09-30 05:53 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-30 01:44 UTCEG score recompute
  71. 2026-09-30 01:44 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-29 13:49 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-09-29 09:42 UTCGHSA enrichmentGHSA-9cp7-7xj6-hh85 · GitHub severity CRITICAL · GitHub CVSS 9.8

Frequently asked(5)

What is CVE-2026-89533?
CVE-2026-89533 is a critical-severity vulnerability; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: svcrdma: Fix offset arithmetic in readchunkrange svcrdmareadchunkrange() walks a Read chunk's segment list to build a sub-range starting at byte offset and spanning length bytes for a Position-Zero or Call chunk. Two arithmetic…
When was the CVE record for CVE-2026-89533 published?
The CVE record for CVE-2026-89533 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-89533 actively exploited?
CVE-2026-89533 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89533?
CVE-2026-89533 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-89533?
A fix for CVE-2026-89533 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89533 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-89533

Explore →

Is Your Infrastructure Affected by CVE-2026-89533?

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