CVE-2026-89688: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-mq7m-fxw5-rr6m
CVSS 9.8
Published
Advisory Summary

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

CVE-2026-89688 at a Glance

CVE Identifier CVE-2026-89688
GHSA Identifier GHSA-mq7m-fxw5-rr6m
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-89688

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-89688, 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: nfsd: drop the stateid, not the stateowner, on seqid_op replay retry In nfs4_preprocess_seqid_op() the stateid is obtained from nfsd4_lookup_stateid(), which holds a reference on the nfs4_stid (sc_count) but takes no reference on the stateowner. openlockstateid() merely casts that stid and likewise takes no reference. When nfsd4_cstate_assign_replay() returns -EAGAIN (the replay owner is being torn down, RP_UNHASHED) it has not taken a stateowner reference on that path. The error handling nevertheless called nfs4_put_stateowner(stp->st_stateowner), dropping an so_count reference the function never acquired -- risking a stateowner refcount underflow and use-after-free -- while leaking the sc_count reference held on the stid. The leaked stid reference can also stall a concurrent nfsd4_close_open_stateid() waiting for sc_count to drop. Drop the reference actually held -- the stid -- before retrying. The stateowner stays alive through the reference held by the stid. This mirrors the open path in nfsd4_process_open1(), where the put balances a reference that path explicitly holds on the stateowner.

References

Frequently Asked Questions

What is CVE-2026-89688?
CVE-2026-89688 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-89688?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-89688?
CVE-2026-89688 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-89688?
CVE-2026-89688 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89688?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mq7m-fxw5-rr6m",
  "modified" : "2026-09-13T09:32:27Z",
  "published" : "2026-09-11T21:31:36Z",
  "aliases" : [ "CVE-2026-89688" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: drop the stateid, not the stateowner, on seqid_op replay retry\n\nIn nfs4_preprocess_seqid_op() the stateid is obtained from\nnfsd4_lookup_stateid(), which holds a reference on the nfs4_stid\n(sc_count) but takes no reference on the stateowner. openlockstateid()\nmerely casts that stid and likewise takes no reference.\n\nWhen nfsd4_cstate_assign_replay() returns -EAGAIN (the replay owner is\nbeing torn down, RP_UNHASHED) it has not taken a stateowner reference on\nthat path. The error handling nevertheless called\nnfs4_put_stateowner(stp->st_stateowner), dropping an so_count reference\nthe function never acquired -- risking a stateowner refcount underflow and\nuse-after-free -- while leaking the sc_count reference held on the stid.\nThe leaked stid reference can also stall a concurrent\nnfsd4_close_open_stateid() waiting for sc_count to drop.\n\nDrop the reference actually held -- the stid -- before retrying. The\nstateowner stays alive through the reference held by the stid. This mirrors\nthe open path in nfsd4_process_open1(), where the put balances a reference\nthat path explicitly holds on the stateowner.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89688"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/00843074d9b84824552c9679d423d29500ca5de0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5e4627d3513e60accfce9d5f4c7fa95251ef93d6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/69ed78b6b947c9257213164678b4edf17533093b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f7cb90ddc021747fc9abfd4cf5252d425fd34eec"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:55Z"
  }
}