CVE-2026-89651: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-vqxr-6xh4-gccq
CVSS 9.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-89651
GHSA Identifier GHSA-vqxr-6xh4-gccq
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-89651

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-89651, 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: ceph: bound MDSCapAuth path and fs_name decode in handle_session() handle_session() decodes the MDSCapAuth records carried by a CEPH_SESSION_OPEN message (msg_version >= 6). For each record the match.path and match.fs_name byte strings are read by first decoding a 32-bit length and then copying that many bytes with the bare ceph_decode_copy(). Unlike the surrounding fields, which all use the _safe decode variants, these two copies are not preceded by a ceph_decode_need() bounds check, and the enclosing MDSCapAuth and MDSCapMatch struct_len fields are skipped rather than enforced as an upper bound. A length larger than the bytes remaining in the message front makes ceph_decode_copy() read past the end of the front buffer. The message front is a dedicated allocation (ceph_msg_new2() -> kvmalloc), so the over-read runs off that object. A malicious or compromised MDS can trigger this with the first post-connect message on mount, with no client-side user interaction; under KASAN it is reported as a slab-out-of-bounds read in handle_session(). Impact: a malicious MDS can force the kernel client to read up to 4 GiB past the message front allocation during session setup, crashing the client (out-of-bounds read). Switch both copies to ceph_decode_copy_safe(), which performs the ceph_decode_need() bounds check before the copy and branches to the existing bad label, matching the rest of the decoder and the error path that frees the partially decoded cap_auths array.

References

Frequently Asked Questions

What is CVE-2026-89651?
CVE-2026-89651 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-89651?
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-89651?
CVE-2026-89651 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-89651?
CVE-2026-89651 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89651?
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-vqxr-6xh4-gccq",
  "modified" : "2026-09-13T09:32:26Z",
  "published" : "2026-09-11T21:31:35Z",
  "aliases" : [ "CVE-2026-89651" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nceph: bound MDSCapAuth path and fs_name decode in handle_session()\n\nhandle_session() decodes the MDSCapAuth records carried by a\nCEPH_SESSION_OPEN message (msg_version >= 6). For each record the\nmatch.path and match.fs_name byte strings are read by first decoding a\n32-bit length and then copying that many bytes with the bare\nceph_decode_copy(). Unlike the surrounding fields, which all use the\n_safe decode variants, these two copies are not preceded by a\nceph_decode_need() bounds check, and the enclosing MDSCapAuth and\nMDSCapMatch struct_len fields are skipped rather than enforced as an\nupper bound. A length larger than the bytes remaining in the message\nfront makes ceph_decode_copy() read past the end of the front buffer.\n\nThe message front is a dedicated allocation (ceph_msg_new2() ->\nkvmalloc), so the over-read runs off that object. A malicious or\ncompromised MDS can trigger this with the first post-connect message on\nmount, with no client-side user interaction; under KASAN it is reported\nas a slab-out-of-bounds read in handle_session().\n\nImpact: a malicious MDS can force the kernel client to read up to 4 GiB\npast the message front allocation during session setup, crashing the\nclient (out-of-bounds read).\n\nSwitch both copies to ceph_decode_copy_safe(), which performs the\nceph_decode_need() bounds check before the copy and branches to the\nexisting bad label, matching the rest of the decoder and the error path\nthat frees the partially decoded cap_auths array.",
  "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-89651"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5f892c767b30e4fb0c744c59f9235c717383d2cd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/77933e22adfe813be2bd10be08d6e950103c3967"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c37db86d2b5e9b57001ccae7e7a727e95a4f9c02"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dc5c7dffda92ef372fa587c444a1c537373df824"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:51Z"
  }
}