CVE-2026-90236: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-frqj-gv5h-9hcc
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90236
GHSA Identifier GHSA-frqj-gv5h-9hcc
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-90236

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-90236, 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: Release the export reference when reaping open stateids nfs4_put_stid() releases the svc_export tracked in nfs4_stid.sc_export, but free_ol_stateid_reaplist() frees open and lock stateids by calling ->sc_free() directly, bypassing that path. An open stateid takes an sc_export reference in nfs4_open() and a lock stateid takes its own in init_lock_stateid(); both reach free_ol_stateid_reaplist() through their normal teardown, the open stateid via release_open_stateid() and the lock stateid via nfsd4_release_lockowner(), each through put_ol_stateid_locked(). The reference is therefore never dropped, pinning the export and blocking unmount for the lifetime of the stateid. Release sc_export in free_ol_stateid_reaplist() the way nfs4_put_stid() does. ->sc_free() runs once per stateid, and a stateid reaches free_ol_stateid_reaplist() or nfs4_put_stid() but never both, so the reference is dropped exactly once. Revoked stateids reach this path with sc_export already cleared by drop_stid_export(), so they are skipped rather than double-freed. nfs4_put_stid() itself read sc_export before acquiring cl_lock. drop_stid_export() clears that field and releases the reference under cl_lock, so a concurrent revocation could drop the export in the window between the read and the final put, releasing the same reference twice. Read sc_export while cl_lock is held so the two paths serialize and the reference is released exactly once.

References

NVD — CVE-2026-90236 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90236
git.kernel.org/stable/c/6480bd7036... WEB
https://git.kernel.org/stable/c/6480bd703684ed3f760e9e36c4a699033c0806ae
git.kernel.org/stable/c/7458727fd7... WEB
https://git.kernel.org/stable/c/7458727fd7cb79d09e5120b6fecc1ad11cdb0946

Frequently Asked Questions

What is CVE-2026-90236?
CVE-2026-90236 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-90236?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90236?
CVE-2026-90236 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90236?
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-frqj-gv5h-9hcc",
  "modified" : "2026-09-17T18:31:57Z",
  "published" : "2026-09-17T18:31:57Z",
  "aliases" : [ "CVE-2026-90236" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Release the export reference when reaping open stateids\n\nnfs4_put_stid() releases the svc_export tracked in\nnfs4_stid.sc_export, but free_ol_stateid_reaplist() frees open and\nlock stateids by calling ->sc_free() directly, bypassing that path.\nAn open stateid takes an sc_export reference in nfs4_open() and a\nlock stateid takes its own in init_lock_stateid(); both reach\nfree_ol_stateid_reaplist() through their normal teardown, the open\nstateid via release_open_stateid() and the lock stateid via\nnfsd4_release_lockowner(), each through put_ol_stateid_locked().\nThe reference is therefore never dropped, pinning the export and\nblocking unmount for the lifetime of the stateid.\n\nRelease sc_export in free_ol_stateid_reaplist() the way\nnfs4_put_stid() does. ->sc_free() runs once per stateid, and a\nstateid reaches free_ol_stateid_reaplist() or nfs4_put_stid() but\nnever both, so the reference is dropped exactly once. Revoked\nstateids reach this path with sc_export already cleared by\ndrop_stid_export(), so they are skipped rather than double-freed.\n\nnfs4_put_stid() itself read sc_export before acquiring cl_lock.\ndrop_stid_export() clears that field and releases the reference\nunder cl_lock, so a concurrent revocation could drop the export in\nthe window between the read and the final put, releasing the same\nreference twice. Read sc_export while cl_lock is held so the two\npaths serialize and the reference is released exactly once.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90236"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6480bd703684ed3f760e9e36c4a699033c0806ae"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7458727fd7cb79d09e5120b6fecc1ad11cdb0946"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:19Z"
  }
}