CVE-2026-98289: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-3rq9-mjhw-q3g6
Share
Published
Advisory Summary

CVE-2026-98289 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-98289 at a Glance

CVE Identifier CVE-2026-98289
GHSA Identifier GHSA-3rq9-mjhw-q3g6
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-98289

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-98289, 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: af_unix: Unify scc_index when finalising SCC in __unix_walk_scc(). Commit bfdb01283ee8 ("af_unix: Assign a unique index to SCC.") changed Tarjan's algorithm to update lowlink with lowlink, which is called lowpoint (unix_vertex.scc_index). unix_vertex_dead() assumes all vertices in an SCC share the same lowpoint, but this is not always true if an SCC has two or more back edges, depending on the order of DFS. For example, the graph below has two back edges from B to A and from C to B. A --> B --> C ^ | ^ | `----' `----' If DFS walks through A -> B -> C -> B (-> C -> B) -> A (-> B -> A), each index and scc_index will be updated as follows. A --> B --> C C = (3, 3) (index, scc_index) B = (2, 2) A = (1, 1) A ... B ... C C = (3, 2)<-. ^ | B = (2, 2) -' `----' A = (1, 1) A ... B ... C C = (3, 2) ^ | . . B = (2, 1)<-. `----' .... A = (1, 1) -' Then, unix_vertex_dead() thinks that B is passed to another SCC with scc_index 2, and the SCC is not garbage-collected. This does not happen if DFS walks in a different order below or starts from B. 1 3 A --> B --> C ^ | ^ | `----' `----' 2 4 Let's unify scc_index across the SCC when finalising it. Note that updating v->index was previously done in unix_scc_dead(), when called from __unix_walk_scc(), just to save one loop. Since __unix_walk_scc() now iterates over the SCC anyway, the update is moved back to __unix_walk_scc() and 'fast' argument is dropped.

References

NVD — CVE-2026-98289 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98289
git.kernel.org/stable/c/4a4263dfea... WEB
https://git.kernel.org/stable/c/4a4263dfeabad72f95e8ab6e15146861fa4144dd
git.kernel.org/stable/c/b8f71d6938... WEB
https://git.kernel.org/stable/c/b8f71d69380a5fbc734c868acbeb560f1de1766f
git.kernel.org/stable/c/be550ee108... WEB
https://git.kernel.org/stable/c/be550ee108ad80828aa61280400bedfc7e7c39d3

Frequently Asked Questions

What is CVE-2026-98289?
CVE-2026-98289 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-98289?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98289?
CVE-2026-98289 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98289?
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-3rq9-mjhw-q3g6",
  "modified" : "2026-10-06T09:31:33Z",
  "published" : "2026-10-06T09:31:33Z",
  "aliases" : [ "CVE-2026-98289" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Unify scc_index when finalising SCC in __unix_walk_scc().\n\nCommit bfdb01283ee8 (\"af_unix: Assign a unique index to SCC.\")\nchanged Tarjan's algorithm to update lowlink with lowlink,\nwhich is called lowpoint (unix_vertex.scc_index).\n\nunix_vertex_dead() assumes all vertices in an SCC share the same\nlowpoint, but this is not always true if an SCC has two or more\nback edges, depending on the order of DFS.\n\nFor example, the graph below has two back edges from B to A\nand from C to B.\n\n  A --> B --> C\n  ^    | ^    |\n  `----' `----'\n\nIf DFS walks through A -> B -> C -> B (-> C -> B) -> A (-> B -> A),\neach index and scc_index will be updated as follows.\n\n  A --> B --> C    C = (3, 3)  (index, scc_index)\n                   B = (2, 2)\n                   A = (1, 1)\n\n  A ... B ... C    C = (3, 2)<-.\n         ^    |    B = (2, 2) -'\n         `----'    A = (1, 1)\n\n  A ... B ... C    C = (3, 2)\n  ^    | .    .    B = (2, 1)<-.\n  `----'  ....     A = (1, 1) -'\n\nThen, unix_vertex_dead() thinks that B is passed to another\nSCC with scc_index 2, and the SCC is not garbage-collected.\n\nThis does not happen if DFS walks in a different order below\nor starts from B.\n\n    1      3\n  A --> B --> C\n  ^    | ^    |\n  `----' `----'\n     2      4\n\nLet's unify scc_index across the SCC when finalising it.\n\nNote that updating v->index was previously done in unix_scc_dead(),\nwhen called from __unix_walk_scc(), just to save one loop.  Since\n__unix_walk_scc() now iterates over the SCC anyway, the update is\nmoved back to __unix_walk_scc() and 'fast' argument is dropped.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98289"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4a4263dfeabad72f95e8ab6e15146861fa4144dd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b8f71d69380a5fbc734c868acbeb560f1de1766f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/be550ee108ad80828aa61280400bedfc7e7c39d3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-06T09:18:19Z"
  }
}