CVE-2026-74401: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-wgc9-j6gh-934m
Share
CVSS 9.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-74401
GHSA Identifier GHSA-wgc9-j6gh-934m
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-74401

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-74401, 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: dlm: fix add msg handle in send_queue ordered In a benchmark scenario triggering a lot of requests that triggers a lot of DLM messages on the network it can be that the mh->seq is not ordered according the oldest seq number. This ordering is required by dlm_receive_ack as "before(mh->seq, seq)" will stop to check for older sequence numbers that are ordered in the tail of "node->send_queue". The side effects of not having it correct ordered regarding "before(mh->seq, seq)" are refcounting issues and use-after free. I only was able to reproduce this issue in a experimental DLM branch and a user space DLM benchmark that uses io_uring. After changing this I don't experienced any refcounting with the sending buffer issues anymore.

References

NVD — CVE-2026-74401 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-74401
git.kernel.org/stable/c/4d45250b1d... WEB
https://git.kernel.org/stable/c/4d45250b1d22960f86d83245be188b16e456218b
git.kernel.org/stable/c/6369619f1b... WEB
https://git.kernel.org/stable/c/6369619f1b665f12d8c99cc6ff733c64eb08b22e
git.kernel.org/stable/c/712714f818... WEB
https://git.kernel.org/stable/c/712714f818d83373847874ab0f8e426be79296cf
git.kernel.org/stable/c/ae9e534e50... WEB
https://git.kernel.org/stable/c/ae9e534e502a0f48c12baf83608c5de0ff0eab11
git.kernel.org/stable/c/d2248cb70c... WEB
https://git.kernel.org/stable/c/d2248cb70c070f8f04762872772e155b59016f17

Frequently Asked Questions

What is CVE-2026-74401?
CVE-2026-74401 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-74401?
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-74401?
CVE-2026-74401 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-74401?
CVE-2026-74401 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-74401?
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-wgc9-j6gh-934m",
  "modified" : "2026-08-17T06:33:43Z",
  "published" : "2026-08-15T06:32:32Z",
  "aliases" : [ "CVE-2026-74401" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndlm: fix add msg handle in send_queue ordered\n\nIn a benchmark scenario triggering a lot of requests that triggers a lot\nof DLM messages on the network it can be that the mh->seq is not ordered\naccording the oldest seq number. This ordering is required by\ndlm_receive_ack as \"before(mh->seq, seq)\" will stop to check for older\nsequence numbers that are ordered in the tail of \"node->send_queue\".\n\nThe side effects of not having it correct ordered regarding\n\"before(mh->seq, seq)\" are refcounting issues and use-after free.\n\nI only was able to reproduce this issue in a experimental DLM branch\nand a user space DLM benchmark that uses io_uring. After changing this I\ndon't experienced any refcounting with the sending buffer issues anymore.",
  "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-74401"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4d45250b1d22960f86d83245be188b16e456218b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6369619f1b665f12d8c99cc6ff733c64eb08b22e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/712714f818d83373847874ab0f8e426be79296cf"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ae9e534e502a0f48c12baf83608c5de0ff0eab11"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d2248cb70c070f8f04762872772e155b59016f17"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:42Z"
  }
}