CVE-2026-72196: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-7v7p-59m6-6h9x
CVSS 8.4
Published
Advisory Summary

CVE-2026-72196 is a HIGH (CVSS 8.4) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-72196 at a Glance

CVE Identifier CVE-2026-72196
GHSA Identifier GHSA-7v7p-59m6-6h9x
Severity HIGH
CVSS v3.1 Base Score 8.4
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.4

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

Attack Vector Local (AV:L)
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-72196

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-72196, 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: bound copy_lcns dp->page_lcns[] index in analysis pass In log_replay()'s analysis pass, after find_dp() returns a valid DIR_PAGE_ENTRY for the (target_attr, target_vcn) tuple, the copy_lcns block walks lrh->lcns_follow further entries: t16 = le16_to_cpu(lrh->lcns_follow); for (i = 0; i < t16; i++) { size_t j = (size_t)(le64_to_cpu(lrh->target_vcn) - le64_to_cpu(dp->vcn)); dp->page_lcns[j + i] = lrh->page_lcns[i]; } find_dp() only validates that target_vcn falls within [dp->vcn, dp->vcn + dp->lcns_follow), i.e., that the FIRST cluster is covered. The walk through the further entries is not bounded against dp->lcns_follow. For a malformed LRH where target_vcn = dp->vcn + dp->lcns_follow - 1 and lrh->lcns_follow > 1, the i > 0 writes overflow the dp's allocated page_lcns[] array. Add the missing j + lrh->lcns_follow <= dp->lcns_follow guard. Reproduced under UML+KASAN on mainline 8d90b09e6741 as a slab-out-of-bounds write of size 8 from log_replay+0x68d4 on the mount path. This is distinct from Pavitra Jha's 2026-05-02 patch ("fs/ntfs3: validate lcns_follow in log_replay conversion", <20260502154252.164586-1-jhapavitra98@gmail.com>) which addresses the separate version-0 dirty-page-table conversion path's memmove(&dp->vcn, ...) call. The two fixes are complementary; both should land. [almaz.alexandrovich@paragon-software.com: clang-formatted the changes, fixed conflicts]

References

Frequently Asked Questions

What is CVE-2026-72196?
CVE-2026-72196 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-72196?
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-72196?
CVE-2026-72196 has a CVSS v3.1 base score of 8.4 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-72196?
CVE-2026-72196 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72196?
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-7v7p-59m6-6h9x",
  "modified" : "2026-08-17T06:33:15Z",
  "published" : "2026-08-15T06:32:15Z",
  "aliases" : [ "CVE-2026-72196" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: bound copy_lcns dp->page_lcns[] index in analysis pass\n\nIn log_replay()'s analysis pass, after find_dp() returns a\nvalid DIR_PAGE_ENTRY for the (target_attr, target_vcn) tuple,\nthe copy_lcns block walks lrh->lcns_follow further entries:\n\n\tt16 = le16_to_cpu(lrh->lcns_follow);\n\tfor (i = 0; i < t16; i++) {\n\t    size_t j = (size_t)(le64_to_cpu(lrh->target_vcn) -\n\t                        le64_to_cpu(dp->vcn));\n\t    dp->page_lcns[j + i] = lrh->page_lcns[i];\n\t}\n\nfind_dp() only validates that target_vcn falls within\n[dp->vcn, dp->vcn + dp->lcns_follow), i.e., that the FIRST\ncluster is covered.  The walk through the further entries is\nnot bounded against dp->lcns_follow.  For a malformed LRH\nwhere target_vcn = dp->vcn + dp->lcns_follow - 1 and\nlrh->lcns_follow > 1, the i > 0 writes overflow the dp's\nallocated page_lcns[] array.\n\nAdd the missing j + lrh->lcns_follow <= dp->lcns_follow guard.\n\nReproduced under UML+KASAN on mainline 8d90b09e6741 as a\nslab-out-of-bounds write of size 8 from log_replay+0x68d4 on\nthe mount path.\n\nThis is distinct from Pavitra Jha's 2026-05-02 patch\n(\"fs/ntfs3: validate lcns_follow in log_replay conversion\",\n<20260502154252.164586-1-jhapavitra98@gmail.com>) which\naddresses the separate version-0 dirty-page-table conversion\npath's memmove(&dp->vcn, ...) call.  The two fixes are\ncomplementary; both should land.\n\n[almaz.alexandrovich@paragon-software.com: clang-formatted the changes,\nfixed conflicts]",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/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-72196"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0f13e823bf86bd1800168ea0bb5bca8b8500a81c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/49c86dae0c0ccb8d98ddcdc46987259389c816dd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5e7b598660cfa8e5af172cf4c65cffc126333307"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9b3d8cc9d54fcded4de51b2b1026ae7182512077"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9b7c28d8c61bdb041936222a09a708531a1c2921"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d240cd98f5f7b65c90f6b2b6abe3232ccdc405ab"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:38Z"
  }
}