CVE-2026-98491

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-10-18. 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

Also known asEUVD-2026-103731 (ENISA EUVD) · GHSA-xf3m-wp4c-wrgw (GitHub Security Advisories)Source: ENISA EUVD

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:

net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry

In a case where skb with an unconfirmed ct entry gets cloned, we may end up committing both but with different sets of extensions.

The series of events:

  • The first clone wants to commit and runs the helpers wiring up
the extension pointer into the expectation list.
  • Then it looses the confirmation keeping the entry unconfirmed.
  • Second clone now wants to commit labels and adds the new extension
for that breaking the pointer in the expectation list causing UAF on the destruction path later.

While this is possible to trigger, there should be no practical network pipeline where committing both clones without modifications into the same zone is needed. So, let's just reset the entry in case for some reason we got an skb with a shared one during commit. This doesn't affect any known use cases, but avoids any potential problems with sharing and modification of the unconfirmed ct entry.

The fixes tag points to the introduction of helpers, since that's the main UAF trigger for the sharing.

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.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
6th
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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-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, 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

October 18, 2026

Last Modified

October 24, 2026

Advisory Details (8)

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

net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/707c2dc77891a874f4e8c52c285a511079164ec8
Web page

net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/55e5256adf3940e71802e2f749cacf81518726b0
Web page

net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/457e0df1b5711fbeb7ba1b6bfd826f5ef30e7e55
Web page

net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37e3c878b183a115f9a114067f9ef3b408ad27fb
Web page

net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26b2bd70d22457556e2fa01cbf1192cb1a94d619

Vendor Advisories for CVE-2026-98491(2)

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

Patch Availability(16)

These rows come from Ubuntu. 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, 6.12.111-1~deb12u1
  • every version up to 6.12.113-1~deb12u1: fixed in 6.12.113-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (36 versions)
  • every version up to 6.12.113-1: fixed in 6.12.113-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (184 versions)
  • every version up to 7.2.9-1: fixed in 7.2.9-1
—

Additional Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 9× in last 7d / 43× 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.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-11-17 18:33 UTCEchelonGraph re-scored
  6. 2026-11-17 18:33 UTCVendor advisory
  7. 2026-11-17 18:33 UTCGHSA enrichmentGHSA-xf3m-wp4c-wrgw · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-11-16 16:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-11-15 14:21 UTCEchelonGraph re-scored
  12. 2026-11-15 14:21 UTCVendor advisory
  13. 2026-11-15 14:21 UTCGHSA enrichmentGHSA-xf3m-wp4c-wrgw · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-11-08 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-11-08 06:21 UTCEchelonGraph re-scored
  22. 2026-11-08 06:21 UTCVendor advisory
  23. 2026-11-08 06:21 UTCGHSA enrichmentGHSA-xf3m-wp4c-wrgw · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 36 more
  1. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-31 22:26 UTCEchelonGraph re-scored
  7. 2026-10-31 22:26 UTCVendor advisory
  8. 2026-10-31 22:26 UTCGHSA enrichmentGHSA-xf3m-wp4c-wrgw · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-25 13:47 UTCEchelonGraph re-scored
  17. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-24 14:26 UTCEchelonGraph re-scored
  19. 2026-10-24 14:26 UTCVendor advisory
  20. 2026-10-24 14:26 UTCGHSA enrichmentGHSA-xf3m-wp4c-wrgw
  21. 2026-10-24 14:14 UTCEchelonGraph re-scoredFirst assessed: 7.8 HIGH
  22. 2026-10-24 14:14 UTCVendor advisory
  23. 2026-10-24 14:14 UTCGHSA enrichmentGHSA-xf3m-wp4c-wrgw
  24. 2026-10-24 14:13 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  25. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  26. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  29. 2026-10-19 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  30. 2026-10-19 10:49 UTCGHSA enrichmentGHSA-xf3m-wp4c-wrgw
  31. 2026-10-19 10:26 UTCNVD update
  32. 2026-10-19 10:01 UTCGHSA enrichmentGHSA-xf3m-wp4c-wrgw
  33. 2026-10-19 09:39 UTCMITRE cvelistV5
  34. 2026-10-18 16:25 UTCNVD update
  35. 2026-10-18 15:20 UTCEchelonGraph re-scored
  36. 2026-10-18 15:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98491?
CVE-2026-98491 is a high-severity vulnerability; its CVE record was published on October 18, 2026. In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry In a case where skb with an unconfirmed ct entry gets cloned, we may end up committing both but with different sets of extensions. The series of events: 1.…
When was the CVE record for CVE-2026-98491 published?
The CVE record for CVE-2026-98491 was published on October 18, 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 24, 2026; the record at its source may have been updated since.
Is CVE-2026-98491 actively exploited?
CVE-2026-98491 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98491?
CVE-2026-98491 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-98491?
A fix for CVE-2026-98491 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98491 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-98491

Explore →

Is Your Infrastructure Affected by CVE-2026-98491?

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