CVE-2026-52989: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-m4w6-2g7f-9j5p
CVSS 9.8
CWE-390 CWE-908
Published
Advisory Summary

CVE-2026-52989 is a CRITICAL (CVSS 9.8) security vulnerability vulnerability (CWE-390: Detection of Error Condition Without Action) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product detects a specific error, but takes no actions to handle the error.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-52989 at a Glance

CVE Identifier CVE-2026-52989
GHSA Identifier GHSA-m4w6-2g7f-9j5p
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-390: Detection of Error Condition Without Action
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-52989

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-52989, 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 CWE-390: Detection of Error Condition Without Action, where the product detects a specific error, but takes no actions to handle the error. 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: propagate nvmet_tcp_build_pdu_iovec() errors to its callers Currently, when nvmet_tcp_build_pdu_iovec() detects an out-of-bounds PDU length or offset, it triggers nvmet_tcp_fatal_error(cmd->queue) and returns early. However, because the function returns void, the callers are entirely unaware that a fatal error has occurred and that the cmd->recv_msg.msg_iter was left uninitialized. Callers such as nvmet_tcp_handle_h2c_data_pdu() proceed to blindly overwrite the queue state with queue->rcv_state = NVMET_TCP_RECV_DATA Consequently, the socket receiving loop may attempt to read incoming network data into the uninitialized iterator. Fix this by shifting the error handling responsibility to the callers.

References

Frequently Asked Questions

What is CVE-2026-52989?
CVE-2026-52989 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-390: Detection of Error Condition Without Action.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-52989?
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-52989?
CVE-2026-52989 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-52989?
CVE-2026-52989 is classified under CWE-390: Detection of Error Condition Without Action (The product detects a specific error, but takes no actions to handle the error.).
How can I check Maven dependencies for CVE-2026-52989?
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-m4w6-2g7f-9j5p",
  "modified" : "2026-06-30T03:37:12Z",
  "published" : "2026-06-24T18:32:43Z",
  "aliases" : [ "CVE-2026-52989" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers\n\nCurrently, when nvmet_tcp_build_pdu_iovec() detects an out-of-bounds\nPDU length or offset, it triggers nvmet_tcp_fatal_error(cmd->queue)\nand returns early. However, because the function returns void, the\ncallers are entirely unaware that a fatal error has occurred and\nthat the cmd->recv_msg.msg_iter was left uninitialized.\n\nCallers such as nvmet_tcp_handle_h2c_data_pdu() proceed to blindly\noverwrite the queue state with queue->rcv_state = NVMET_TCP_RECV_DATA\nConsequently, the socket receiving loop may attempt to read incoming\nnetwork data into the uninitialized iterator.\n\nFix this by shifting the error handling responsibility to the callers.",
  "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-52989"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/security/cve/CVE-2026-52989"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2492443"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/046fa5c72d15cd8e2d592e275697ea399d8f76b0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3df42a854686fa06484e37ac1a3931c8e3e3453c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c2a11441538bdbbc5aa003f190995eba93a89b88"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d7c8f95f599b3b38a717d2e771c3f8c174f657c3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ea8e356acb165cb1fd75537a52e1f66e5e76c538"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f9204a2b78dd18374d3bcf9bf93d9021ce22de1b"
  }, {
    "type" : "WEB",
    "url" : "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52989.json"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-390", "CWE-908" ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-06-24T17:17:09Z"
  }
}