CVE-2026-72192: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-gc6w-qcf3-4mhm
CVSS 9.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-72192
GHSA Identifier GHSA-gc6w-qcf3-4mhm
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-72192

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-72192, 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: ntfs3: bound to_move in indx_insert_into_root before hdr_insert_head indx_insert_into_root() promotes a full resident $INDEX_ROOT into $INDEX_ALLOCATION and copies all non-last resident root entries into a newly allocated INDEX_BUFFER via hdr_insert_head(). The source byte count 'to_move' is summed from the on-disk resident entry sizes and is independent of the destination buffer size, which comes from root->index_block_size (via indx->index_bits). A crafted NTFS image that keeps a valid, full resident root but shrinks root->index_block_size down to 512 after the root has been populated makes hdr_insert_head() memcpy attacker-controlled resident entry bytes past the end of the kmalloc(1u << indx->index_bits) allocation returned by indx_new(). For a 512-byte destination and a resident root whose non-last entries total 560 bytes, the memcpy overruns by 120 bytes and a following memmove extends the highest written offset to 136 bytes past the allocation. The overflow bytes are a direct copy of on-disk entries (via kmemdup), so they are fully attacker-controlled. The write is reachable from unprivileged open(O_CREAT) on a mounted crafted NTFS image: a single sufficiently long create in a directory whose resident root is already full forces root promotion and triggers the copy. This is a controlled out-of-bounds write of 120-136 bytes past a kmalloc(index_block_size) allocation, with attacker-controlled content. It is a bounded adjacent-heap corruption primitive; it is not an arbitrary-address write. Successful exploitation into a named victim object depends on the surrounding slab layout. Reject the copy at the sink. The destination's INDEX_HDR already reports hdr_total (the payload capacity of the new buffer) and hdr_used (the bytes already consumed by the terminal END entry installed by indx_new()); require that to_move fits in the remaining payload before calling hdr_insert_head(). On mismatch, fail with -EINVAL and mark the filesystem as having a detected on-disk inconsistency, which is the same behaviour as the surrounding validation in this function.

References

Frequently Asked Questions

What is CVE-2026-72192?
CVE-2026-72192 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-72192?
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-72192?
CVE-2026-72192 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-72192?
CVE-2026-72192 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72192?
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-gc6w-qcf3-4mhm",
  "modified" : "2026-08-17T06:33:15Z",
  "published" : "2026-08-15T06:32:15Z",
  "aliases" : [ "CVE-2026-72192" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs3: bound to_move in indx_insert_into_root before hdr_insert_head\n\nindx_insert_into_root() promotes a full resident $INDEX_ROOT into\n$INDEX_ALLOCATION and copies all non-last resident root entries into\na newly allocated INDEX_BUFFER via hdr_insert_head(). The source\nbyte count 'to_move' is summed from the on-disk resident entry sizes\nand is independent of the destination buffer size, which comes from\nroot->index_block_size (via indx->index_bits).\n\nA crafted NTFS image that keeps a valid, full resident root but\nshrinks root->index_block_size down to 512 after the root has been\npopulated makes hdr_insert_head() memcpy attacker-controlled resident\nentry bytes past the end of the kmalloc(1u << indx->index_bits)\nallocation returned by indx_new(). For a 512-byte destination and a\nresident root whose non-last entries total 560 bytes, the memcpy\noverruns by 120 bytes and a following memmove extends the highest\nwritten offset to 136 bytes past the allocation. The overflow bytes\nare a direct copy of on-disk entries (via kmemdup), so they are\nfully attacker-controlled.\n\nThe write is reachable from unprivileged open(O_CREAT) on a mounted\ncrafted NTFS image: a single sufficiently long create in a directory\nwhose resident root is already full forces root promotion and\ntriggers the copy.\n\nThis is a controlled out-of-bounds write of 120-136 bytes past a\nkmalloc(index_block_size) allocation, with attacker-controlled\ncontent. It is a bounded adjacent-heap corruption primitive; it is\nnot an arbitrary-address write. Successful exploitation into a named\nvictim object depends on the surrounding slab layout.\n\nReject the copy at the sink. The destination's INDEX_HDR already\nreports hdr_total (the payload capacity of the new buffer) and\nhdr_used (the bytes already consumed by the terminal END entry\ninstalled by indx_new()); require that to_move fits in the remaining\npayload before calling hdr_insert_head(). On mismatch, fail with\n-EINVAL and mark the filesystem as having a detected on-disk\ninconsistency, which is the same behaviour as the surrounding\nvalidation in this function.",
  "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-72192"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0af83b8155cc848e9f5d2c36e20a70d024214649"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/194b00c99ba971fa7cf6acd747a36032c6de54eb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/53c5f3b2da3774b41534728aba295c098c9efa19"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9b6926ac9c970ae0b2c2fe6289b16e9aa10b6a67"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aaa1f956c0fc41089a4a534da7df91552a08a47c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cb3161deebcaf8d36d3115abf452c633f2180fc1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d240f5f9d036b8180224954d9873f172b6be4dd8"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:37Z"
  }
}