CVE-2026-72190: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-72190 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-72190 at a Glance
How to Fix CVE-2026-72190
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-72190, 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-72190?
Which Software versions are affected?
What version fixes CVE-2026-72190?
What CWE is associated with CVE-2026-72190?
How can I check Maven dependencies for CVE-2026-72190?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-7xmj-mqhm-5492",
"modified" : "2026-08-15T06:32:15Z",
"published" : "2026-08-15T06:32:15Z",
"aliases" : [ "CVE-2026-72190" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: fix mrec_lock ABBA deadlock in rename\n\nntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an\ninode's mrec_lock before taking the mrec_lock of its parent directory.\n\nntfs_rename() takes old_ni->mrec_lock and old_dir_ni->mrec_lock\nbefore taking new_ni->mrec_lock for an existing target, or\nnew_dir_ni->mrec_lock for a cross-directory rename.\nThis can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds\nthe target inode, or when ntfs_dir_fsync() holds a child target\ndirectory, while rename() holds the parent directory and waits for the\ntarget.\n\nFix this by locking the existing target inode before taking any parent\ndirectory mrec_lock. For cross-directory renames where the target parent\nis a descendant of the source parent, lock the target parent before the\nsource parent so the directory order matches the child-to-parent order used\nby ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72190"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/b3d09502b80dfe0bab9090ca532710da389f6c7f"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/eb94f5a41a193a425e09a63cb75dffd151d8f42e"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-15T06:21:37Z"
}
}