CVE-2026-64057: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-8264-g9fh-vx2h
Share
CVSS 7.8
CWE-667
Published
Advisory Summary

CVE-2026-64057 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-667: Improper Locking) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-64057 at a Glance

CVE Identifier CVE-2026-64057
GHSA Identifier GHSA-8264-g9fh-vx2h
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification CWE-667: Improper Locking
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

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

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
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-64057

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-64057, 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 CWE-667: Improper Locking, where the product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. 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: afs: Fix the locking used by afs_get_link() The afs filesystem in the kernel doesn't do locking correctly for symbolic links. There are a number of problems: (1) It doesn't do any locking around afs_read_single() to prevent races between multiple ->get_link() calls, thereby allowing the possibility of leaks. (2) It doesn't use RCU barriering when accessing the buffer pointers during RCU pathwalk. (3) It can race with another thread updating the contents of the symlink if a third party updated it on the server. Fix this by the following means: (0) Move symlink handling into its own file as this makes it more complicated. (1) Take the validate_lock around afs_read_single() to prevent races between multiple ->get_link() calls. (2) Keep a separate copy of the symlink contents with an rcu_head. This is always going to be a lot smaller than a page, so it can be kmalloc'd and save quite a bit of memory. It also needs a refcount for non-RCU pathwalk. (3) Split the symlink read and write-to-cache routines in afs from those for directories. (4) Discard the I/O buffer as soon as the write-to-cache completes as this is a full page (plus a folio_queue). (5) If there's no cache, discard the I/O buffer immediately after reading and copying if there is no cache.

References

NVD — CVE-2026-64057 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-64057
git.kernel.org/stable/c/77ea917cbe... WEB
https://git.kernel.org/stable/c/77ea917cbed62882a33114b1e23ededb977e4287
git.kernel.org/stable/c/93531bca46... WEB
https://git.kernel.org/stable/c/93531bca46707c6c28c4f4eb26c101fa36ccb8cb
git.kernel.org/stable/c/c0410adf3d... WEB
https://git.kernel.org/stable/c/c0410adf3da6db46f3513411fcf95e63c2f1d1ad

Frequently Asked Questions

What is CVE-2026-64057?
CVE-2026-64057 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-667: Improper Locking.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-64057?
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-64057?
CVE-2026-64057 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-64057?
CVE-2026-64057 is classified under CWE-667: Improper Locking (The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.).
How can I check Maven dependencies for CVE-2026-64057?
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-8264-g9fh-vx2h",
  "modified" : "2026-10-15T12:30:39Z",
  "published" : "2026-07-19T18:31:50Z",
  "aliases" : [ "CVE-2026-64057" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nafs: Fix the locking used by afs_get_link()\n\nThe afs filesystem in the kernel doesn't do locking correctly for symbolic\nlinks.  There are a number of problems:\n\n (1) It doesn't do any locking around afs_read_single() to prevent races\n     between multiple ->get_link() calls, thereby allowing the possibility\n     of leaks.\n\n (2) It doesn't use RCU barriering when accessing the buffer pointers\n     during RCU pathwalk.\n\n (3) It can race with another thread updating the contents of the symlink\n     if a third party updated it on the server.\n\nFix this by the following means:\n\n (0) Move symlink handling into its own file as this makes it more\n     complicated.\n\n (1) Take the validate_lock around afs_read_single() to prevent races\n     between multiple ->get_link() calls.\n\n (2) Keep a separate copy of the symlink contents with an rcu_head.  This\n     is always going to be a lot smaller than a page, so it can be\n     kmalloc'd and save quite a bit of memory.  It also needs a refcount\n     for non-RCU pathwalk.\n\n (3) Split the symlink read and write-to-cache routines in afs from those\n     for directories.\n\n (4) Discard the I/O buffer as soon as the write-to-cache completes as this\n     is a full page (plus a folio_queue).\n\n (5) If there's no cache, discard the I/O buffer immediately after reading\n     and copying if there is no cache.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64057"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/77ea917cbed62882a33114b1e23ededb977e4287"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/93531bca46707c6c28c4f4eb26c101fa36ccb8cb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c0410adf3da6db46f3513411fcf95e63c2f1d1ad"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-667" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-19T16:17:46Z"
  }
}