CVE-2026-89968: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-46h3-r5w2-2vqq
Share
CVSS 7.5
Published
Advisory Summary

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

CVE-2026-89968 at a Glance

CVE Identifier CVE-2026-89968
GHSA Identifier GHSA-46h3-r5w2-2vqq
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

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:N/I:N/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 None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-89968

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-89968, 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: nvmet-tcp: reject unsolicited H2CData PDUs nvmet_tcp_handle_h2c_data_pdu() accepts an H2CData PDU after only checking that its TTAG is a valid in-range command index and that the command's data buffers are mapped. It never checks that the target has actually solicited that data by sending an R2T for the command. A remote host can abuse this. It submits a write command that takes the R2T path and, before the target transmits the R2T, sends an H2CData PDU for that command's tag. The data completes the command early, and when the command then fails synchronously (e.g. a length mismatch caught by nvmet_check_transfer_len()), it is completed a second time. Each completion calls nvmet_tcp_queue_response(), so the same command is added to queue->resp_list twice while it is still linked; the second llist_add() makes the node point to itself (lentry->next == lentry). nvmet_tcp_process_resp_list() then walks that self-referential node and adds the command to resp_send_list twice. With CONFIG_DEBUG_LIST this trips the "list_add double add" check (kernel BUG); without it the loop never terminates and the nvmet_tcp workqueue wedges (soft-lockup). It is remotely triggerable and needs no authentication on an allow_any_host subsystem. Track whether an R2T has been transmitted for a command and reject an H2CData PDU that arrives before it. The flag is cleared on command reuse (nvmet_tcp_get_cmd() zeroes cmd->flags) and stays set across the multiple H2CData PDUs of a single solicited transfer.

References

NVD — CVE-2026-89968 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89968
git.kernel.org/stable/c/02341ee424... WEB
https://git.kernel.org/stable/c/02341ee424fb2eed16b5b8a9d247492e49335c21
git.kernel.org/stable/c/14beef7d4f... WEB
https://git.kernel.org/stable/c/14beef7d4f123fb458fc9844aa74a071871dcca6
git.kernel.org/stable/c/1cbed75389... WEB
https://git.kernel.org/stable/c/1cbed7538946c99e585acefd11c9ba3a0bdbae05
git.kernel.org/stable/c/2b71f9193e... WEB
https://git.kernel.org/stable/c/2b71f9193e3d3a352920ba367f1a6db345249038
git.kernel.org/stable/c/9fb527103e... WEB
https://git.kernel.org/stable/c/9fb527103e53fd43a8e802c2eca407869c204f7a
git.kernel.org/stable/c/cade124c06... WEB
https://git.kernel.org/stable/c/cade124c06f8e738e3a0df285ed2e08953e6bfaa
git.kernel.org/stable/c/cf1484d9a7... WEB
https://git.kernel.org/stable/c/cf1484d9a75de6809ef331e16f525aaa41b0e16d
git.kernel.org/stable/c/db62b35cbc... WEB
https://git.kernel.org/stable/c/db62b35cbca052860c519cbcabe7650708528738

Frequently Asked Questions

What is CVE-2026-89968?
CVE-2026-89968 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-89968?
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-89968?
CVE-2026-89968 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-89968?
CVE-2026-89968 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89968?
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-46h3-r5w2-2vqq",
  "modified" : "2026-09-16T15:31:03Z",
  "published" : "2026-09-16T12:30:43Z",
  "aliases" : [ "CVE-2026-89968" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: reject unsolicited H2CData PDUs\n\nnvmet_tcp_handle_h2c_data_pdu() accepts an H2CData PDU after only checking\nthat its TTAG is a valid in-range command index and that the command's\ndata buffers are mapped. It never checks that the target has actually\nsolicited that data by sending an R2T for the command.\n\nA remote host can abuse this. It submits a write command that takes the\nR2T path and, before the target transmits the R2T, sends an H2CData PDU\nfor that command's tag. The data completes the command early, and when\nthe command then fails synchronously (e.g. a length mismatch caught by\nnvmet_check_transfer_len()), it is completed a second time. Each\ncompletion calls nvmet_tcp_queue_response(), so the same command is added\nto queue->resp_list twice while it is still linked; the second llist_add()\nmakes the node point to itself (lentry->next == lentry).\n\nnvmet_tcp_process_resp_list() then walks that self-referential node and\nadds the command to resp_send_list twice. With CONFIG_DEBUG_LIST this\ntrips the \"list_add double add\" check (kernel BUG); without it the loop\nnever terminates and the nvmet_tcp workqueue wedges (soft-lockup). It is\nremotely triggerable and needs no authentication on an allow_any_host\nsubsystem.\n\nTrack whether an R2T has been transmitted for a command and reject an\nH2CData PDU that arrives before it. The flag is cleared on command reuse\n(nvmet_tcp_get_cmd() zeroes cmd->flags) and stays set across the multiple\nH2CData PDUs of a single solicited transfer.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89968"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/02341ee424fb2eed16b5b8a9d247492e49335c21"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/14beef7d4f123fb458fc9844aa74a071871dcca6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1cbed7538946c99e585acefd11c9ba3a0bdbae05"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2b71f9193e3d3a352920ba367f1a6db345249038"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9fb527103e53fd43a8e802c2eca407869c204f7a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cade124c06f8e738e3a0df285ed2e08953e6bfaa"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cf1484d9a75de6809ef331e16f525aaa41b0e16d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/db62b35cbca052860c519cbcabe7650708528738"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:07Z"
  }
}