CVE-2026-98068

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.7 under NVD CVSS v3. EPSS exploit probability: <0.1% (below the 1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-86721 (ENISA EUVD) · GHSA-v6pw-c666-7jqh (GitHub Security Advisories)Source: ENISA EUVD

4.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net/rds: don't let rds_conn_shutdown() consume a concurrent drop

rds_conn_shutdown() finishes by moving the path from RDS_CONN_DISCONNECTING to RDS_CONN_DOWN, and also accepts RDS_CONN_ERROR as the starting state of that final transition, so that a FIN processed in softirq context during the teardown does not derail the shutdown into a noisy error path.

But consuming that RDS_CONN_ERROR also consumes the shutdown pass that came with it: rds_conn_path_drop() sets RDS_CONN_ERROR and then queues cp_down_w, and a pass that starts on a path already in RDS_CONN_DOWN is a no-op. For the FIN case that is harmless - the socket the FIN arrived on is the very socket the teardown just released. It is not harmless for a dropper that attached something to the path first.

rds_tcp_accept_one() is such a dropper. Its path claim in rds_tcp_accept_one_path() transitions RDS_CONN_DOWN -> RDS_CONN_CONNECTING, and a concurrent drop - a FIN on a previous socket in softirq context, an administrative reset - can put the path into RDS_CONN_ERROR between that claim and the state check that follows, which accepts RDS_CONN_ERROR. The accept then installs the freshly accepted socket with rds_tcp_set_callbacks() while the queued teardown - which sampled tc->t_sock before this socket existed - is still running. rds_connect_path_complete() fails its transition to RDS_CONN_UP and drops the path again, queueing the pass that should reap the socket it just installed. If the in-flight shutdown's final transition consumes that drop's RDS_CONN_ERROR, the queued pass finds the path in RDS_CONN_DOWN and does nothing. The installed socket is never torn down: it sits established with its callbacks armed and its rds_tcp_connection on rds_tcp_tc_list, the peer sees a connection that nothing ever reads, and the path is wedged in RDS_CONN_DOWN until some later event drops it again. Reproduced with widened race windows as an ever-growing receive queue on a socket owned by a path stuck in RDS_CONN_DOWN, with the peer's send path wedged behind it.

Make the final transition only DISCONNECTING -> DOWN. If it fails because the path is in RDS_CONN_ERROR, a drop raced the teardown: cancel the reconnect timer and clear RDS_RECONNECT_PENDING - the one piece of the skipped tail that must not be left behind - and return, letting the pass the drop queued finish the job: it tears down whatever attached to the path in the meantime, completes the transition to RDS_CONN_DOWN, and re-arms the reconnect from its own tail.

The timer quiesce in that branch matters because the racing drop does not always queue that pass: rds_conn_path_drop() returns without queueing when a destroy is pending - exactly the situation during a netns teardown or module unload, when a FIN on the dying socket is processed while rds_conn_path_destroy() flushes cp_down_w. If the flushed pass is the one that takes this return, no later pass exists, and rds_conn_path_destroy() would find cp_conn_w still armed (WARN_ON) and then free a path whose reconnect timer can still fire. With the cancel in the branch, every exit of a shutdown pass leaves the timer quiesced no matter which pass completes the transition.

The FIN case keeps making progress, one pass later and still without noisy logging. Any other state keeps today's rds_conn_path_error() handling; no current cp_state writer can leave a DISCONNECTING path in anything but RDS_CONN_ERROR (every other writer is a cmpxchg from a non-DISCONNECTING state), so that branch is defensive.

On kernels without the preceding patches the same hazard exists with the sample-based quiesce; the fix applies there equally.

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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.1%
EPSS %ILE
below the 1st
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 (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS. 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, and whom BOD 26-04 binds: 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 (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.

The score's inputs: 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 25, 2026

Last Modified

November 18, 2026

Advisory Details (8)

Auto-updated Nov 18, 2026
Patch available.
Web page

net/rds: don't let rds_conn_shutdown() consume a concurrent drop - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/rds: don't let rds_conn_shutdown() consume a concurrent drop - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/rds: don't let rds_conn_shutdown() consume a concurrent drop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7cb11257aa3e5ef0bedfd5d55ac60bb00347aa97
Web page

net/rds: don't let rds_conn_shutdown() consume a concurrent drop - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/rds: don't let rds_conn_shutdown() consume a concurrent drop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4980ce260205001d582a7b3cb5eab29877777fbc
Web page

net/rds: don't let rds_conn_shutdown() consume a concurrent drop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2941561395066be856a53626d4ca973dd9c982b2
Web page

net/rds: don't let rds_conn_shutdown() consume a concurrent drop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/260c6308fe2e19ad519389d44d582e292aecc3af
Web page

net/rds: don't let rds_conn_shutdown() consume a concurrent drop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ec75c69918b7f6a1a5e3fb6442925246a9ec86b

Vendor Advisories for CVE-2026-98068(2)

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

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1124.133) @ jammy2026-11-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1017.17) @ resolute2026-11-18ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1070.70) @ jammy2026-11-18ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1064.65) @ noble2026-11-18ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1113.111) @ jammy2026-11-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-42.42) @ resolute2026-11-18ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.202.174) @ jammy2026-11-18ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1071.78) @ noble2026-11-18ubuntu
ubuntulinux-tools-realtime-hwe-26.04-edge (7.0.0-43.43.1) @ resolute2026-11-18ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1071.78~22.04.1) @ jammy2026-11-18ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1020.21) @ resolute2026-11-18ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2056.58) @ noble2026-11-18ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1064.65~22.04.1) @ jammy2026-11-18ubuntu
ubuntulinux-vmware-tools-6.8.0-1010 (6.8.0-1010.10) @ noble2026-11-18ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1067.70.1) @ noble2026-11-18ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-149.149~22.04.1) @ jammy2026-11-18ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1039.40) @ noble2026-11-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1023.23) @ resolute2026-11-18ubuntu
linuxKernel @ 5.10.271 (fixes >=4.12.0)—osv

These rows come from Ubuntu and OSV. 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 ... 6.1.99-1 (57 versions)
  • every version up to 6.1.190-1: fixed in 6.1.190-1
—
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 (181 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(18)

Data Freshness Timeline

(refreshed 11× in last 7d / 35× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

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 89 is merged into the row it repeats.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-11-18 18:28 UTCEchelonGraph re-scoredFirst assessed: 4.7 MEDIUM
  5. 2026-11-18 18:28 UTCVendor advisory
  6. 2026-11-18 18:28 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  7. 2026-11-18 18:27 UTCNVD updateCVSS v3 → 4.7 · severity → MEDIUM
  8. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-11-17 19:26 UTCEchelonGraph re-scored
  10. 2026-11-17 19:26 UTCVendor advisory
  11. 2026-11-17 19:26 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  12. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
Show 63 more
  1. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-28 09:25 UTCOSV refresh
  9. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-25 13:47 UTCEchelonGraph re-scored
  13. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-19 10:37 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  19. 2026-10-19 10:25 UTCNVD update
  20. 2026-10-19 09:52 UTCEchelonGraph re-scored
  21. 2026-10-19 09:52 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  22. 2026-10-19 09:39 UTCMITRE cvelistV5
  23. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-10-18 02:56 UTCEchelonGraph re-scored
  25. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-10-12 14:39 UTCEchelonGraph re-scored
  31. 2026-10-11 23:19 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  32. 2026-10-11 19:10 UTCEchelonGraph re-scored
  33. 2026-10-11 16:25 UTCEchelonGraph re-scored
  34. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-10-11 13:37 UTCEchelonGraph re-scored
  36. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  37. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-10-09 03:21 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  39. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  41. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  42. 2026-10-06 07:24 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  43. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  44. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  45. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  46. 2026-10-03 11:27 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  47. 2026-10-03 11:26 UTCNVD update
  48. 2026-10-03 11:12 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  49. 2026-10-03 11:10 UTCMITRE cvelistV5
  50. 2026-10-03 10:35 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  51. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  52. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  54. 2026-09-30 14:35 UTCEchelonGraph re-scored
  55. 2026-09-30 14:35 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  56. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  57. 2026-09-28 07:29 UTCEchelonGraph re-scored
  58. 2026-09-28 07:29 UTCGHSA enrichmentGHSA-v6pw-c666-7jqh
  59. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  60. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  61. 2026-09-25 11:30 UTCNVD update
  62. 2026-09-25 10:27 UTCEchelonGraph re-scored
  63. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98068?
CVE-2026-98068 is a medium-severity vulnerability; its CVE record was published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net/rds: don't let rds_conn_shutdown() consume a concurrent drop rds_conn_shutdown() finishes by moving the path from RDS_CONN_DISCONNECTING to RDS_CONN_DOWN, and also accepts RDS_CONN_ERROR as the starting state of that final…
When was the CVE record for CVE-2026-98068 published?
The CVE record for CVE-2026-98068 was published on September 25, 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 November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-98068 actively exploited?
CVE-2026-98068 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98068?
CVE-2026-98068 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-98068?
A fix for CVE-2026-98068 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98068 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-98068

Explore →

Is Your Infrastructure Affected by CVE-2026-98068?

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