CVE-2026-98491: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-xf3m-wp4c-wrgw
Share
Published
Advisory Summary

CVE-2026-98491 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98491 at a Glance

CVE Identifier CVE-2026-98491
GHSA Identifier GHSA-xf3m-wp4c-wrgw
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98491

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-98491, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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. The first clone wants to commit and runs the helpers wiring up the extension pointer into the expectation list. 2. Then it looses the confirmation keeping the entry unconfirmed. 3. 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.

References

NVD — CVE-2026-98491 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98491
git.kernel.org/stable/c/26b2bd70d2... WEB
https://git.kernel.org/stable/c/26b2bd70d22457556e2fa01cbf1192cb1a94d619
git.kernel.org/stable/c/37e3c878b1... WEB
https://git.kernel.org/stable/c/37e3c878b183a115f9a114067f9ef3b408ad27fb
git.kernel.org/stable/c/457e0df1b5... WEB
https://git.kernel.org/stable/c/457e0df1b5711fbeb7ba1b6bfd826f5ef30e7e55
git.kernel.org/stable/c/55e5256adf... WEB
https://git.kernel.org/stable/c/55e5256adf3940e71802e2f749cacf81518726b0
git.kernel.org/stable/c/707c2dc778... WEB
https://git.kernel.org/stable/c/707c2dc77891a874f4e8c52c285a511079164ec8
git.kernel.org/stable/c/de41ee24f7... WEB
https://git.kernel.org/stable/c/de41ee24f77b0fc45397db3e277cae2adbd43dfe
git.kernel.org/stable/c/e0fa5ea434... WEB
https://git.kernel.org/stable/c/e0fa5ea434b7e8467ef3adc64e3858b1ca2a642d
git.kernel.org/stable/c/e2829ae545... WEB
https://git.kernel.org/stable/c/e2829ae5459ddb5fce526b2e84697edf6c0c3cef

Frequently Asked Questions

What is CVE-2026-98491?
CVE-2026-98491 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98491?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98491?
CVE-2026-98491 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98491?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xf3m-wp4c-wrgw",
  "modified" : "2026-10-18T18:31:51Z",
  "published" : "2026-10-18T18:31:51Z",
  "aliases" : [ "CVE-2026-98491" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: conntrack: avoid modifying shared unconfirmed ct entry\n\nIn a case where skb with an unconfirmed ct entry gets cloned, we may\nend up committing both but with different sets of extensions.\n\nThe series of events:\n\n 1. The first clone wants to commit and runs the helpers wiring up\n    the extension pointer into the expectation list.\n 2. Then it looses the confirmation keeping the entry unconfirmed.\n 3. Second clone now wants to commit labels and adds the new extension\n    for that breaking the pointer in the expectation list causing\n    UAF on the destruction path later.\n\nWhile this is possible to trigger, there should be no practical\nnetwork pipeline where committing both clones without modifications\ninto the same zone is needed.  So, let's just reset the entry in case\nfor some reason we got an skb with a shared one during commit.  This\ndoesn't affect any known use cases, but avoids any potential problems\nwith sharing and modification of the unconfirmed ct entry.\n\nThe fixes tag points to the introduction of helpers, since that's the\nmain UAF trigger for the sharing.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98491"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/26b2bd70d22457556e2fa01cbf1192cb1a94d619"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/37e3c878b183a115f9a114067f9ef3b408ad27fb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/457e0df1b5711fbeb7ba1b6bfd826f5ef30e7e55"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/55e5256adf3940e71802e2f749cacf81518726b0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/707c2dc77891a874f4e8c52c285a511079164ec8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/de41ee24f77b0fc45397db3e277cae2adbd43dfe"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e0fa5ea434b7e8467ef3adc64e3858b1ca2a642d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e2829ae5459ddb5fce526b2e84697edf6c0c3cef"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:00Z"
  }
}