CVE-2026-72199: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-r953-ww6g-j7cw
Share
CVSS 9.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-72199
GHSA Identifier GHSA-r953-ww6g-j7cw
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-72199

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-72199, 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: ntfs: validate resident index root values on lookup Resident $INDEX_ROOT values carry index header fields that callers consume after lookup. Some callers already validate parts of the layout before walking entries, but those checks are scattered and do not cover all root header invariants, such as entries_offset alignment and lower bound, index_length, and allocated_size consistency. The resident root resize paths now keep these header fields consistent while the value size changes: ntfs_ir_truncate() lowers index.allocated_size before shrinking the resident value, and ntfs_ir_reparent() grows the resident value before publishing a larger root header. Lookup-time validation can therefore cover these invariants without tripping over the driver's own resize paths. Add $INDEX_ROOT to the minimum resident value size table and validate the resident index header fields before returning the attribute from lookup. Require 8-byte aligned index header fields, a sane entries_offset, an index_length within allocated_size, allocated_size within the resident value, and enough entry space for at least an index entry header. The shared validator already rejects non-resident records for resident-only attribute types, including $INDEX_ROOT.

References

NVD — CVE-2026-72199 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72199
git.kernel.org/stable/c/bfb01dd319... WEB
https://git.kernel.org/stable/c/bfb01dd319b6b4c3e79756de7b75ccf0b9a0a247
git.kernel.org/stable/c/fcf5bf0e85... WEB
https://git.kernel.org/stable/c/fcf5bf0e8570798970e3ae8c95d04765ba2c5b97

Frequently Asked Questions

What is CVE-2026-72199?
CVE-2026-72199 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-72199?
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-72199?
CVE-2026-72199 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-72199?
CVE-2026-72199 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72199?
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-r953-ww6g-j7cw",
  "modified" : "2026-08-17T06:33:15Z",
  "published" : "2026-08-15T06:32:15Z",
  "aliases" : [ "CVE-2026-72199" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: validate resident index root values on lookup\n\nResident $INDEX_ROOT values carry index header fields that callers\nconsume after lookup. Some callers already validate parts of the layout\nbefore walking entries, but those checks are scattered and do not cover\nall root header invariants, such as entries_offset alignment and lower\nbound, index_length, and allocated_size consistency.\n\nThe resident root resize paths now keep these header fields consistent\nwhile the value size changes: ntfs_ir_truncate() lowers\nindex.allocated_size before shrinking the resident value, and\nntfs_ir_reparent() grows the resident value before publishing a larger\nroot header. Lookup-time validation can therefore cover these invariants\nwithout tripping over the driver's own resize paths.\n\nAdd $INDEX_ROOT to the minimum resident value size table and validate the\nresident index header fields before returning the attribute from lookup.\nRequire 8-byte aligned index header fields, a sane entries_offset, an\nindex_length within allocated_size, allocated_size within the resident\nvalue, and enough entry space for at least an index entry header.\n\nThe shared validator already rejects non-resident records for\nresident-only attribute types, including $INDEX_ROOT.",
  "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-72199"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bfb01dd319b6b4c3e79756de7b75ccf0b9a0a247"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fcf5bf0e8570798970e3ae8c95d04765ba2c5b97"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:38Z"
  }
}