CVE-2026-72344: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-p5q5-g8w9-fgw6
Share
CVSS 7.8
Published
Advisory Summary

CVE-2026-72344 is a HIGH (CVSS 7.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-72344 at a Glance

CVE Identifier CVE-2026-72344
GHSA Identifier GHSA-p5q5-g8w9-fgw6
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
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-72344

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-72344, 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: net/mlx5e: TC, skip peer flow cleanup when LAG seq is unavailable mlx5_lag_get_dev_seq() will return error when the peer isn't in the LAG or when no device is marked as master. Result bad memory access and kernel crash[1]. Hence, skip the peer when lookup fails. Note: In case there are peer flows, they are cleaned before LAG cleared the master mark. [1] RIP: 0010:mlx5e_tc_del_fdb_peers_flow+0x3d/0x350 [mlx5_core] Call Trace: <TASK> mlx5e_tc_clean_fdb_peer_flows+0xc1/0x130 [mlx5_core] mlx5_esw_offloads_unpair+0x3a/0x400 [mlx5_core] mlx5_esw_offloads_devcom_event+0xee/0x360 [mlx5_core] mlx5_devcom_send_event+0x7a/0x140 [mlx5_core] mlx5_esw_offloads_devcom_cleanup+0x2f/0x90 [mlx5_core] mlx5e_tc_esw_cleanup+0x28/0xf0 [mlx5_core] mlx5e_rep_tc_cleanup+0x19/0x30 [mlx5_core] mlx5e_cleanup_uplink_rep_tx+0x36/0x40 [mlx5_core] mlx5e_cleanup_rep_tx+0x55/0x60 [mlx5_core] mlx5e_detach_netdev+0x96/0xf0 [mlx5_core] mlx5e_netdev_change_profile+0x5b/0x120 [mlx5_core] mlx5e_netdev_attach_nic_profile+0x1b/0x30 [mlx5_core] mlx5e_vport_rep_unload+0xdd/0x110 [mlx5_core] __esw_offloads_unload_rep+0x81/0xb0 [mlx5_core] mlx5_eswitch_unregister_vport_reps+0x1d7/0x220 [mlx5_core] mlx5e_rep_remove+0x22/0x30 [mlx5_core] device_release_driver_internal+0x194/0x1f0 bus_remove_device+0xe8/0x1b0 device_del+0x159/0x3c0 mlx5_rescan_drivers_locked+0xbc/0x2d0 [mlx5_core] mlx5_unregister_device+0x54/0x80 [mlx5_core] mlx5_uninit_one+0x73/0x130 [mlx5_core] remove_one+0x78/0xe0 [mlx5_core] pci_device_remove+0x39/0xa0

References

NVD — CVE-2026-72344 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72344
git.kernel.org/stable/c/5a95aa0198... WEB
https://git.kernel.org/stable/c/5a95aa0198af75047d98fb72950642c89dab770f
git.kernel.org/stable/c/7bed4af0ce... WEB
https://git.kernel.org/stable/c/7bed4af0ced82948d660205efecd551ef8bc3912

Frequently Asked Questions

What is CVE-2026-72344?
CVE-2026-72344 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-72344?
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-72344?
CVE-2026-72344 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-72344?
CVE-2026-72344 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72344?
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-p5q5-g8w9-fgw6",
  "modified" : "2026-08-17T06:33:24Z",
  "published" : "2026-08-15T06:32:21Z",
  "aliases" : [ "CVE-2026-72344" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: TC, skip peer flow cleanup when LAG seq is unavailable\n\nmlx5_lag_get_dev_seq() will return error when the peer isn't in the LAG\nor when no device is marked as master. Result bad memory access and kernel\ncrash[1].\n\nHence, skip the peer when lookup fails.\n\nNote: In case there are peer flows, they are cleaned before LAG cleared\nthe master mark.\n\n[1]\nRIP: 0010:mlx5e_tc_del_fdb_peers_flow+0x3d/0x350 [mlx5_core]\nCall Trace:\n <TASK>\n mlx5e_tc_clean_fdb_peer_flows+0xc1/0x130 [mlx5_core]\n mlx5_esw_offloads_unpair+0x3a/0x400 [mlx5_core]\n mlx5_esw_offloads_devcom_event+0xee/0x360 [mlx5_core]\n mlx5_devcom_send_event+0x7a/0x140 [mlx5_core]\n mlx5_esw_offloads_devcom_cleanup+0x2f/0x90 [mlx5_core]\n mlx5e_tc_esw_cleanup+0x28/0xf0 [mlx5_core]\n mlx5e_rep_tc_cleanup+0x19/0x30 [mlx5_core]\n mlx5e_cleanup_uplink_rep_tx+0x36/0x40 [mlx5_core]\n mlx5e_cleanup_rep_tx+0x55/0x60 [mlx5_core]\n mlx5e_detach_netdev+0x96/0xf0 [mlx5_core]\n mlx5e_netdev_change_profile+0x5b/0x120 [mlx5_core]\n mlx5e_netdev_attach_nic_profile+0x1b/0x30 [mlx5_core]\n mlx5e_vport_rep_unload+0xdd/0x110 [mlx5_core]\n __esw_offloads_unload_rep+0x81/0xb0 [mlx5_core]\n mlx5_eswitch_unregister_vport_reps+0x1d7/0x220 [mlx5_core]\n mlx5e_rep_remove+0x22/0x30 [mlx5_core]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xe8/0x1b0\n device_del+0x159/0x3c0\n mlx5_rescan_drivers_locked+0xbc/0x2d0 [mlx5_core]\n mlx5_unregister_device+0x54/0x80 [mlx5_core]\n mlx5_uninit_one+0x73/0x130 [mlx5_core]\n remove_one+0x78/0xe0 [mlx5_core]\n pci_device_remove+0x39/0xa0",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72344"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5a95aa0198af75047d98fb72950642c89dab770f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7bed4af0ced82948d660205efecd551ef8bc3912"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:07Z"
  }
}