CVE-2026-89495: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-3pmg-pq3r-v8mc
CVSS 9.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-89495
GHSA Identifier GHSA-3pmg-pq3r-v8mc
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-89495

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-89495, 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: ocfs2: bound namelen in dlm_migrate_request_handler Patch series "ocfs2/dlm: bound peer-controlled lengths in the o2dlm". The o2dlm receive handlers trust u8 length and count fields from the wire without bounding them, so a node in a DLM domain can corrupt or panic any other node with a malformed message. Three defects: - dlm_migrate_request_handler() passes migrate->namelen unchecked to dlm_init_mle(), which memcpy()s it into the 32-byte mname[] of an o2dlm_mle slab object: a heap out-of-bounds write of up to ~215 attacker-controlled bytes. - dlm_mig_lockres_handler() passes mres->lockname_len unchecked to dlm_init_lockres(), which memcpy()s it into the 32-byte o2dlm_lockname slab object: a heap out-of-bounds write of up to ~223 bytes. - the same handler trusts mres->num_locks without checking that the message is large enough to hold that many entries, so dlm_process_recovery_data() walks mres->ml[] past the kmalloc(data_len) copy and trips a BUG_ON (an out-of-bounds read ending in a panic). The other o2dlm receive handlers already reject an oversized name; the migration and recovery handlers have omitted it since the DLM was added (see the Fixes tags). Patch 1 bounds namelen; patch 2 validates lockname_len, num_locks, and the payload size. Conforming recovery and migration traffic is unaffected. o2net authenticates peers only by the DLM domain key, so any node that has joined the domain -- including a compromised or malicious member -- can send these messages. There is no local trigger; the attacker must already be a member of the cluster. Each sink was confirmed under KASAN with an out-of-tree module mirroring it exactly -- a kmem_cache/kmalloc of the real destination size, then the same unclamped memcpy/loop: slab-out-of-bounds Write for the two writes, Read for the recovery walk, and a panic. A userspace AddressSanitizer build faults identically under -m32 and -m64. Scrubbed logs are available on request. I reported this privately to security@kernel.org and the ocfs2 maintainers on 2026-06-20; with no response after the standard embargo period I am posting the fix publicly. I have no embargo requirement. This patch (of 2): A node receiving a DLM_MIGRATE_REQUEST message trusts the peer-supplied name length (migrate->namelen) without bounding it. dlm_init_mle() then copies that many bytes into the fixed DLM_LOCKID_NAME_MAX-byte mname[] array of an o2dlm_mle slab object, so a malformed message from a cluster peer overflows the slab object by up to ~215 bytes: a heap out-of-bounds write of attacker-controlled data, reachable by any node in the domain. Reject an oversized name, the way dlm_master_request_handler() and the other o2dlm receive handlers already do; the migration handler omits the check entirely. Conforming messages are unaffected.

References

Frequently Asked Questions

What is CVE-2026-89495?
CVE-2026-89495 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-89495?
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-89495?
CVE-2026-89495 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-89495?
CVE-2026-89495 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89495?
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-3pmg-pq3r-v8mc",
  "modified" : "2026-09-14T15:32:27Z",
  "published" : "2026-09-11T21:31:29Z",
  "aliases" : [ "CVE-2026-89495" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: bound namelen in dlm_migrate_request_handler\n\nPatch series \"ocfs2/dlm: bound peer-controlled lengths in the o2dlm\".\n\nThe o2dlm receive handlers trust u8 length and count fields from the wire\nwithout bounding them, so a node in a DLM domain can corrupt or panic any\nother node with a malformed message.  Three defects:\n\n  - dlm_migrate_request_handler() passes migrate->namelen unchecked to\n    dlm_init_mle(), which memcpy()s it into the 32-byte mname[] of an\n    o2dlm_mle slab object: a heap out-of-bounds write of up to ~215\n    attacker-controlled bytes.\n\n  - dlm_mig_lockres_handler() passes mres->lockname_len unchecked to\n    dlm_init_lockres(), which memcpy()s it into the 32-byte o2dlm_lockname\n    slab object: a heap out-of-bounds write of up to ~223 bytes.\n\n  - the same handler trusts mres->num_locks without checking that the\n    message is large enough to hold that many entries, so\n    dlm_process_recovery_data() walks mres->ml[] past the kmalloc(data_len)\n    copy and trips a BUG_ON (an out-of-bounds read ending in a panic).\n\nThe other o2dlm receive handlers already reject an oversized name; the\nmigration and recovery handlers have omitted it since the DLM was added\n(see the Fixes tags).  Patch 1 bounds namelen; patch 2 validates\nlockname_len, num_locks, and the payload size.  Conforming recovery and\nmigration traffic is unaffected.\n\no2net authenticates peers only by the DLM domain key, so any node that has\njoined the domain -- including a compromised or malicious member -- can\nsend these messages.  There is no local trigger; the attacker must already\nbe a member of the cluster.\n\nEach sink was confirmed under KASAN with an out-of-tree module mirroring\nit exactly -- a kmem_cache/kmalloc of the real destination size, then the\nsame unclamped memcpy/loop: slab-out-of-bounds Write for the two writes,\nRead for the recovery walk, and a panic.  A userspace AddressSanitizer\nbuild faults identically under -m32 and -m64.  Scrubbed logs are available\non request.\n\nI reported this privately to security@kernel.org and the ocfs2 maintainers\non 2026-06-20; with no response after the standard embargo period I am\nposting the fix publicly.  I have no embargo requirement.\n\n\nThis patch (of 2):\n\nA node receiving a DLM_MIGRATE_REQUEST message trusts the peer-supplied\nname length (migrate->namelen) without bounding it.  dlm_init_mle() then\ncopies that many bytes into the fixed DLM_LOCKID_NAME_MAX-byte mname[]\narray of an o2dlm_mle slab object, so a malformed message from a cluster\npeer overflows the slab object by up to ~215 bytes: a heap out-of-bounds\nwrite of attacker-controlled data, reachable by any node in the domain.\n\nReject an oversized name, the way dlm_master_request_handler() and the\nother o2dlm receive handlers already do; the migration handler omits the\ncheck entirely.  Conforming messages are unaffected.",
  "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-89495"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/006c96ea488eca2ef5155ec76038e0a4dbf65f0a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2487bea2098322669f0563baff53e797486b823f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/24989909d3413b44b104102caa6661b1e424ba0f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aabc5d8388e6f8826345f0073455dbcaaaa6491d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/de10cd3b062a5235af754925fcf49beb5a1109d4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e1288865b8ceac0dcd1009ecba43de961f13d5bd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ea5b5609305a8437bc955a0834a530c12246d78f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f8658ee3327f73bd81c0bcd07cdeb5a8527fac98"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:31Z"
  }
}