CVE-2026-72187: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-72187 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.
CVE-2026-72187 at a Glance
How to Fix CVE-2026-72187
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.
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-72187, 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
References
Frequently Asked Questions
What is CVE-2026-72187?
Which Software versions are affected?
What version fixes CVE-2026-72187?
What CWE is associated with CVE-2026-72187?
How can I check Maven dependencies for CVE-2026-72187?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-f35h-7767-j6v8",
"modified" : "2026-08-15T06:32:15Z",
"published" : "2026-08-15T06:32:15Z",
"aliases" : [ "CVE-2026-72187" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: avoid self-deadlock during inode eviction\n\nAn attribute-list update performed while allocating clusters can drop the\nlast reference to the temporary attribute inode. Evicting that inode\ndrops its reference to the base inode and can invoke ntfs_drop_big_inode()\nfor the base inode from within the base inode's own writeback path.\n\nIf the base inode is unlinked, ntfs_drop_big_inode() calls\ntruncate_setsize(), which waits for the inode's folio writeback to\ncomplete. The same writeback worker is responsible for completing that\nwriteback, so it waits for itself indefinitely.\n\nPrevent this self-deadlock by grabbing a reference to the base inode at the\nbeginning of ntfs_writepages() and releasing it at the end of the function.\nThis defers eviction until all bios have been submitted, allowing the wait\nfor folio writeback to complete safely.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72187"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/5a5f877c5df7605e9bae524a25ec0df9b9cb8ea8"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/77dc384207d5fa63ba97c3bf3285fe1215a1cbf6"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-15T06:21:37Z"
}
}