CVE-2026-72411: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-426f-jh2p-2383
Share
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-72411
GHSA Identifier GHSA-426f-jh2p-2383
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-72411

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-72411, 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: dsa: mxl862xx: fix use-after-free of DSA ports in crc_err_work Upon an MDIO CRC error mxl862xx_crc_err_work_fn() walks the DSA ports and closes the CPU port conduits: dsa_switch_for_each_cpu_port(dp, priv->ds) dev_close(dp->conduit); mxl862xx_remove() unregisters the switch before cancelling this work: set_bit(MXL862XX_FLAG_WORK_STOPPED, &priv->flags); cancel_delayed_work_sync(&priv->stats_work); dsa_unregister_switch(ds); mxl862xx_host_shutdown(priv); dsa_unregister_switch() frees the dsa_port objects. If a CRC error schedules the work during teardown it can run after the ports have been freed and dereference freed memory. Guard the port walk with MXL862XX_FLAG_WORK_STOPPED, which is already set before dsa_unregister_switch(). DSA tears the ports down under rtnl_lock(), so checking the flag under rtnl_lock() means the work either runs before teardown and sees valid ports, or runs afterwards, observes the flag and skips the walk. This mirrors the host_flood_work handler, which skips torn-down ports under rtnl_lock().

References

NVD — CVE-2026-72411 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72411
git.kernel.org/stable/c/bcb3b83146... WEB
https://git.kernel.org/stable/c/bcb3b8314611ed9cb4ff4bff484ef9b154fd1b83
git.kernel.org/stable/c/cf52622fbc... WEB
https://git.kernel.org/stable/c/cf52622fbc274eb4ca9a2066b258da2ae3dc7406

Frequently Asked Questions

What is CVE-2026-72411?
CVE-2026-72411 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-72411?
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-72411?
CVE-2026-72411 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-72411?
CVE-2026-72411 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72411?
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-426f-jh2p-2383",
  "modified" : "2026-08-17T06:33:28Z",
  "published" : "2026-08-15T06:32:23Z",
  "aliases" : [ "CVE-2026-72411" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: mxl862xx: fix use-after-free of DSA ports in crc_err_work\n\nUpon an MDIO CRC error mxl862xx_crc_err_work_fn() walks the DSA ports\nand closes the CPU port conduits:\n\n\tdsa_switch_for_each_cpu_port(dp, priv->ds)\n\t\tdev_close(dp->conduit);\n\nmxl862xx_remove() unregisters the switch before cancelling this work:\n\n\tset_bit(MXL862XX_FLAG_WORK_STOPPED, &priv->flags);\n\tcancel_delayed_work_sync(&priv->stats_work);\n\tdsa_unregister_switch(ds);\n\tmxl862xx_host_shutdown(priv);\n\ndsa_unregister_switch() frees the dsa_port objects. If a CRC error\nschedules the work during teardown it can run after the ports have been\nfreed and dereference freed memory.\n\nGuard the port walk with MXL862XX_FLAG_WORK_STOPPED, which is already set\nbefore dsa_unregister_switch(). DSA tears the ports down under\nrtnl_lock(), so checking the flag under rtnl_lock() means the work either\nruns before teardown and sees valid ports, or runs afterwards, observes\nthe flag and skips the walk. This mirrors the host_flood_work handler,\nwhich skips torn-down ports under rtnl_lock().",
  "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-72411"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bcb3b8314611ed9cb4ff4bff484ef9b154fd1b83"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cf52622fbc274eb4ca9a2066b258da2ae3dc7406"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:14Z"
  }
}