CVE-2026-89667: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-f2vv-wrgm-2rrj
Share
CVSS 8.1
Published
Advisory Summary

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

CVE-2026-89667 at a Glance

CVE Identifier CVE-2026-89667
GHSA Identifier GHSA-f2vv-wrgm-2rrj
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.1

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

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
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-89667

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-89667, 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: close shrinker/GC/fsnotify vs per-net shutdown race in filecache The shrinker, GC worker, and fsnotify/lease callbacks can unhash an nfsd_file from the rhashtable and then call nfsd_file_dispose_list_delayed() to move it to the per-net dispose list. If nfsd_file_cache_shutdown_net() runs concurrently, its rhashtable walk misses the already-unhashed file, and its drain of the per-net dispose list can run before the file has been queued. The file then sits on the per-net list with no thread to drain it, leaking both the file and its associated state. The GC worker and shrinker already hold nfsd_gc_lock while walking the LRU, but in the original code they release it before calling nfsd_file_dispose_list_delayed(). The fsnotify/lease path (nfsd_file_close_inode) has no synchronization at all. Fix this by: 1. Widening nfsd_gc_lock in both nfsd_file_gc() and nfsd_file_lru_scan() to cover the nfsd_file_dispose_list_delayed() call. 2. Wrapping nfsd_file_close_inode() in nfsd_gc_lock so that all three callers of nfsd_file_dispose_list_delayed() hold the lock. 3. Adding a spin_lock/unlock(nfsd_gc_lock) barrier in nfsd_file_cache_shutdown_net() after the purge, so that any in-progress disposal has fully completed before the per-net list is drained. All operations inside the lock are non-sleeping (rhashtable lookups, atomic bit/refcount ops, list moves, svc_wake_up), so the spinlock is appropriate.

References

NVD — CVE-2026-89667 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89667
git.kernel.org/stable/c/08af9593e2... WEB
https://git.kernel.org/stable/c/08af9593e2b472fd98c00faf1bf03bdbb7203477
git.kernel.org/stable/c/40162cfea7... WEB
https://git.kernel.org/stable/c/40162cfea79b9510380decfdd1795b754dc9f972
git.kernel.org/stable/c/6d6b9f6a75... WEB
https://git.kernel.org/stable/c/6d6b9f6a75c3767250e9c23ace4e384ab8f7843e
git.kernel.org/stable/c/b15997b53b... WEB
https://git.kernel.org/stable/c/b15997b53b61c74fb4d083f7261d19f389ff854f

Frequently Asked Questions

What is CVE-2026-89667?
CVE-2026-89667 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-89667?
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-89667?
CVE-2026-89667 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-89667?
CVE-2026-89667 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89667?
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-f2vv-wrgm-2rrj",
  "modified" : "2026-09-21T15:31:36Z",
  "published" : "2026-09-11T21:31:35Z",
  "aliases" : [ "CVE-2026-89667" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: close shrinker/GC/fsnotify vs per-net shutdown race in filecache\n\nThe shrinker, GC worker, and fsnotify/lease callbacks can unhash an\nnfsd_file from the rhashtable and then call\nnfsd_file_dispose_list_delayed() to move it to the per-net dispose list.\nIf nfsd_file_cache_shutdown_net() runs concurrently, its rhashtable walk\nmisses the already-unhashed file, and its drain of the per-net dispose\nlist can run before the file has been queued.  The file then sits on\nthe per-net list with no thread to drain it, leaking both the file and\nits associated state.\n\nThe GC worker and shrinker already hold nfsd_gc_lock while walking the\nLRU, but in the original code they release it before calling\nnfsd_file_dispose_list_delayed().  The fsnotify/lease path\n(nfsd_file_close_inode) has no synchronization at all.\n\nFix this by:\n\n  1. Widening nfsd_gc_lock in both nfsd_file_gc() and nfsd_file_lru_scan()\n     to cover the nfsd_file_dispose_list_delayed() call.\n\n  2. Wrapping nfsd_file_close_inode() in nfsd_gc_lock so that all three\n     callers of nfsd_file_dispose_list_delayed() hold the lock.\n\n  3. Adding a spin_lock/unlock(nfsd_gc_lock) barrier in\n     nfsd_file_cache_shutdown_net() after the purge, so that any\n     in-progress disposal has fully completed before the per-net list\n     is drained.\n\nAll operations inside the lock are non-sleeping (rhashtable lookups,\natomic bit/refcount ops, list moves, svc_wake_up), so the spinlock is\nappropriate.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/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-89667"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/08af9593e2b472fd98c00faf1bf03bdbb7203477"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/40162cfea79b9510380decfdd1795b754dc9f972"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6d6b9f6a75c3767250e9c23ace4e384ab8f7843e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b15997b53b61c74fb4d083f7261d19f389ff854f"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:53Z"
  }
}