CVE-2026-72377: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-72377 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-72377 at a Glance
How to Fix CVE-2026-72377
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-72377, 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-72377?
Which Software versions are affected?
What version fixes CVE-2026-72377?
What CWE is associated with CVE-2026-72377?
How can I check Maven dependencies for CVE-2026-72377?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-jw6q-qfr2-5f75",
"modified" : "2026-08-15T06:32:22Z",
"published" : "2026-08-15T06:32:22Z",
"aliases" : [ "CVE-2026-72377" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nafs: Remove setting of AS_RELEASE_ALWAYS for symlinks and mountpoints\n\nRegular AFS files correctly use afs_file_aops which have release_folio\nset as netfs_release_folio, so AS_RELEASE_ALWAYS is valid for them\nwhen fscache is enabled (set via afs_vnode_set_cache()).\nSymlinks and mountpoints in AFS use afs_dir_aops, which does not provide\na release_folio callback. However, afs_apply_status() unconditionally\ncalls mapping_set_release_always() for these.\n\nIn such case when memory management code attempts to release folios,\nfilemap_release_folio() checks folio_needs_release() which\nreturns true due to AS_RELEASE_ALWAYS being set. Since there is no\nrelease_folio callback, it falls through to try_to_free_buffers(),\nwhich at present expects buffer_heads to be not null. For symlinks\nand mountpoints without buffer_heads, this causes pointer dereference.\n\n[dh: Added more bits that were missed]",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72377"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/81e985b4c3a6cbcc443fcdcd3ebda7fcc845d459"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9d6b0f6d437e2f8350e08678e5e1d20c11c364f3"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-15T06:22:11Z"
}
}