CVE-2026-72470: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-mxhq-w28g-hr4q
Share
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-72470
GHSA Identifier GHSA-mxhq-w28g-hr4q
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-72470

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-72470, 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: fs/ntfs3: resize log->one_page_buf when adopting on-disk page size log_replay() allocates log->one_page_buf using the page size that was chosen from the host PAGE_SIZE: log->one_page_buf = kmalloc(log->page_size, GFP_NOFS); Later, when a restart area is found, the log page size recorded on disk is adopted: t32 = le32_to_cpu(log->rst_info.r_page->sys_page_size); if (log->page_size != t32) { log->l_size = log->orig_file_size; log->page_size = norm_file_page(t32, &log->l_size, t32 == DefaultLogPageSize); } If the on-disk page size is larger than the size used for the initial allocation, log->page_size grows but one_page_buf is left at its original, smaller size. A subsequent unaligned read_log_page() then reads log->page_size bytes into the undersized scratch buffer: page_buf = page_off ? log->one_page_buf : *buffer; err = ntfs_read_run_nb_ra(ni->mi.sbi, &ni->file.run, page_vbo, page_buf, log->page_size, NULL, &log->read_ahead); overflowing the allocation. This is reachable when mounting a dirty NTFS volume whose log was formatted with a page size larger than the buffer initially allocated on the mounting host (for example a 64K-log volume mounted on a host that allocated a 4K scratch buffer). Grow one_page_buf when the adopted on-disk page size exceeds the size used for the initial allocation. On krealloc() failure the original buffer is left intact and freed by the existing error path.

References

NVD — CVE-2026-72470 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72470
git.kernel.org/stable/c/2097a2537d... WEB
https://git.kernel.org/stable/c/2097a2537d9d1c29c0e20ed0dbf717a0ccd8f374
git.kernel.org/stable/c/4f129fc6f7... WEB
https://git.kernel.org/stable/c/4f129fc6f756f8541e5bff45b1804cc11b1ec712
git.kernel.org/stable/c/5a35454179... WEB
https://git.kernel.org/stable/c/5a35454179fe1041d9cd286f5d320ce0d448c12a
git.kernel.org/stable/c/c99444f6df... WEB
https://git.kernel.org/stable/c/c99444f6dfca893f6d310aae4a53c620f98f7b4f
git.kernel.org/stable/c/f1422df595... WEB
https://git.kernel.org/stable/c/f1422df595d69b997d23a8f11e12c528ccef7fad

Frequently Asked Questions

What is CVE-2026-72470?
CVE-2026-72470 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-72470?
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-72470?
CVE-2026-72470 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-72470?
CVE-2026-72470 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72470?
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-mxhq-w28g-hr4q",
  "modified" : "2026-08-17T06:33:31Z",
  "published" : "2026-08-15T06:32:25Z",
  "aliases" : [ "CVE-2026-72470" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: resize log->one_page_buf when adopting on-disk page size\n\nlog_replay() allocates log->one_page_buf using the page size that was\nchosen from the host PAGE_SIZE:\n\n\tlog->one_page_buf = kmalloc(log->page_size, GFP_NOFS);\n\nLater, when a restart area is found, the log page size recorded on disk\nis adopted:\n\n\tt32 = le32_to_cpu(log->rst_info.r_page->sys_page_size);\n\tif (log->page_size != t32) {\n\t\tlog->l_size = log->orig_file_size;\n\t\tlog->page_size = norm_file_page(t32, &log->l_size,\n\t\t\t\t\t\tt32 == DefaultLogPageSize);\n\t}\n\nIf the on-disk page size is larger than the size used for the initial\nallocation, log->page_size grows but one_page_buf is left at its\noriginal, smaller size. A subsequent unaligned read_log_page() then\nreads log->page_size bytes into the undersized scratch buffer:\n\n\tpage_buf = page_off ? log->one_page_buf : *buffer;\n\terr = ntfs_read_run_nb_ra(ni->mi.sbi, &ni->file.run, page_vbo, page_buf,\n\t\t\t\t  log->page_size, NULL, &log->read_ahead);\n\noverflowing the allocation. This is reachable when mounting a dirty\nNTFS volume whose log was formatted with a page size larger than the\nbuffer initially allocated on the mounting host (for example a 64K-log\nvolume mounted on a host that allocated a 4K scratch buffer).\n\nGrow one_page_buf when the adopted on-disk page size exceeds the size\nused for the initial allocation. On krealloc() failure the original\nbuffer is left intact and freed by the existing error path.",
  "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-72470"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2097a2537d9d1c29c0e20ed0dbf717a0ccd8f374"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4f129fc6f756f8541e5bff45b1804cc11b1ec712"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5a35454179fe1041d9cd286f5d320ce0d448c12a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c99444f6dfca893f6d310aae4a53c620f98f7b4f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f1422df595d69b997d23a8f11e12c528ccef7fad"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:21Z"
  }
}