CVE-2026-64062: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-pw37-pjm5-88jp
Share
CVSS 5.5
CWE-667
Published
Advisory Summary

CVE-2026-64062 is a MODERATE (CVSS 5.5) 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-64062 at a Glance

CVE Identifier CVE-2026-64062
GHSA Identifier GHSA-pw37-pjm5-88jp
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-667: Improper Locking
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

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:N/I:N/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 None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-64062

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-64062, 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: netfs: Fix potential deadlock in write-through mode Fix netfs_advance_writethrough() to always unlock the supplied folio and to mark it dirty if it isn't yet written to the end. Unfortunately, it can't be marked for writeback until the folio is done with as that may cause a deadlock against mmapped reads and writes. Even though it has been marked dirty, premature writeback can't occur as the caller is holding both inode->i_rwsem (which will prevent concurrent truncation, fallocation, DIO and other writes) and ictx->wb_lock (which will cause flushing to wait and writeback to skip or wait). Note that this may be easier to deal with once the queuing of folios is split from the generation of subrequests.

References

NVD — CVE-2026-64062 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-64062
git.kernel.org/stable/c/003aa0dd26... WEB
https://git.kernel.org/stable/c/003aa0dd26c964025acd6d1213bcdbd674db2ca9
git.kernel.org/stable/c/1468f39243... WEB
https://git.kernel.org/stable/c/1468f39243ccb155b6d97f9a9932f610d1205d75
git.kernel.org/stable/c/b6a4ae1634... WEB
https://git.kernel.org/stable/c/b6a4ae1634b3ad2aaa05222e53d36da532852faf
git.kernel.org/stable/c/e40e9cbf3e... WEB
https://git.kernel.org/stable/c/e40e9cbf3ee4d30ee9a97bd128c85500b6ad0da1

Frequently Asked Questions

What is CVE-2026-64062?
CVE-2026-64062 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-64062?
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-64062?
CVE-2026-64062 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-64062?
CVE-2026-64062 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-64062?
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-pw37-pjm5-88jp",
  "modified" : "2026-09-02T21:31:50Z",
  "published" : "2026-07-19T18:31:51Z",
  "aliases" : [ "CVE-2026-64062" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfs: Fix potential deadlock in write-through mode\n\nFix netfs_advance_writethrough() to always unlock the supplied folio and to\nmark it dirty if it isn't yet written to the end.  Unfortunately, it can't\nbe marked for writeback until the folio is done with as that may cause a\ndeadlock against mmapped reads and writes.\n\nEven though it has been marked dirty, premature writeback can't occur as\nthe caller is holding both inode->i_rwsem (which will prevent concurrent\ntruncation, fallocation, DIO and other writes) and ictx->wb_lock (which\nwill cause flushing to wait and writeback to skip or wait).\n\nNote that this may be easier to deal with once the queuing of folios is\nsplit from the generation of subrequests.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64062"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/003aa0dd26c964025acd6d1213bcdbd674db2ca9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1468f39243ccb155b6d97f9a9932f610d1205d75"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b6a4ae1634b3ad2aaa05222e53d36da532852faf"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e40e9cbf3ee4d30ee9a97bd128c85500b6ad0da1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-667" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-19T16:17:46Z"
  }
}