CVE-2026-90095: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-f6c3-623p-967p
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90095
GHSA Identifier GHSA-f6c3-623p-967p
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-90095

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-90095, 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: fuse: Fix the condition to enable over-io-uring The existing condition in fuse_uring_cmd() is there only to avoid disabling io-uring for connections that already run with it, missing was a condition to refuse any IORING_OP_URING_CMD if the connection/channel didn't get enabled because of missing FUSE_INIT reply flag FUSE_OVER_IO_URING. Without the reply flag the barrier in fuse_uring_ready() doesn't work and IO could already be going on and cause deadlock states (at a minimum one between fch->bg_lock and queue->lock). The change itself is trivial, but brings behavior change, FUSE_OVER_IO_URING has to be set in the FUSE_INIT_REPLY by fuse servers to accept any IORING_OP_URING_CMD. Libfuse does that and the only non-libfuse implementation I found (fractal-fuse) also does it. Qemu patches for fuse-io-uring are not merged yet, as far as I know. Moved up is the smp_load_acquire(&fch->initialized) check, as a fuse-server implementation might try to setup io-uring before FUSE_INIT is processed and might have gotten -EOPNOTSUPP instead of -EAGAIN. Also fixed is a stale comment that explains the handling of the FUSE_OVER_IO_URING flag in early RFC versions. If there should be a report from any library or application we probably need to revert this commit.

References

NVD — CVE-2026-90095 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90095
git.kernel.org/stable/c/1ca1df82d9... WEB
https://git.kernel.org/stable/c/1ca1df82d9248fc0b5ff17d45607484f18e5d60b
git.kernel.org/stable/c/1f59015e95... WEB
https://git.kernel.org/stable/c/1f59015e958174e89be58cc8db16d70a60d17255
git.kernel.org/stable/c/8f9a725d89... WEB
https://git.kernel.org/stable/c/8f9a725d89711ad027f6b7183586ef91528f106d

Frequently Asked Questions

What is CVE-2026-90095?
CVE-2026-90095 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-90095?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90095?
CVE-2026-90095 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90095?
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-f6c3-623p-967p",
  "modified" : "2026-10-15T12:30:47Z",
  "published" : "2026-09-17T18:31:50Z",
  "aliases" : [ "CVE-2026-90095" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfuse: Fix the condition to enable over-io-uring\n\nThe existing condition in fuse_uring_cmd() is there only to avoid\ndisabling io-uring for connections that already run with it, missing\nwas a condition to refuse any IORING_OP_URING_CMD if the\nconnection/channel didn't get enabled because of missing FUSE_INIT\nreply flag FUSE_OVER_IO_URING. Without the reply flag the barrier in\nfuse_uring_ready() doesn't work and IO could already be going on and\ncause deadlock states (at a minimum one between fch->bg_lock and\nqueue->lock).\n\nThe change itself is trivial, but brings behavior change,\nFUSE_OVER_IO_URING has to be set in the FUSE_INIT_REPLY by fuse servers\nto accept any IORING_OP_URING_CMD. Libfuse does that and the only\nnon-libfuse implementation I found (fractal-fuse) also does it.\nQemu patches for fuse-io-uring are not merged yet, as far as I know.\n\nMoved up is the smp_load_acquire(&fch->initialized) check, as a\nfuse-server implementation might try to setup io-uring before FUSE_INIT\nis processed and might have gotten -EOPNOTSUPP instead of -EAGAIN.\n\nAlso fixed is a stale comment that explains the handling of the\nFUSE_OVER_IO_URING flag in early RFC versions.\n\nIf there should be a report from any library or application we\nprobably need to revert this commit.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90095"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1ca1df82d9248fc0b5ff17d45607484f18e5d60b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1f59015e958174e89be58cc8db16d70a60d17255"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8f9a725d89711ad027f6b7183586ef91528f106d"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:01Z"
  }
}