CVE-2026-64015: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-6rrm-p5j2-8pf8
Share
CVSS 7.8
CWE-362 CWE-125
Published
Advisory Summary

CVE-2026-64015 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-64015 at a Glance

CVE Identifier CVE-2026-64015
GHSA Identifier GHSA-6rrm-p5j2-8pf8
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
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-64015

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-64015, 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-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), where the product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. 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: security/keys: fix missed RCU read section on lookup Nicholas Carlini reports that the keyring code calls assoc_array_find() in find_key_to_update() without holding the RCU read lock, while the assoc_array_gc() code really is designed around removing the node from the tree and then freeing it after an RCU grace-period. The regular key handling doesn't see this because holding the keyring semaphore hides any lifetime issues, but the persistent key handling uses a different model. Instead of extending the keyring locking, just do the simple RCU locking that the assoc_array was designed for.

References

NVD — CVE-2026-64015 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-64015
git.kernel.org/stable/c/43a1e37445... WEB
https://git.kernel.org/stable/c/43a1e3744548e6fd85873e6fb43e293eb4010694
git.kernel.org/stable/c/4c5d407ba3... WEB
https://git.kernel.org/stable/c/4c5d407ba3ff7f30561ff73ba1b07ed70c864edc
git.kernel.org/stable/c/50bb3435a5... WEB
https://git.kernel.org/stable/c/50bb3435a5e627bfbdc52eb4536f49f88b3486b8
git.kernel.org/stable/c/5659e6923c... WEB
https://git.kernel.org/stable/c/5659e6923cb72f8e18e8b539109ab512455fe195
git.kernel.org/stable/c/66288dcadf... WEB
https://git.kernel.org/stable/c/66288dcadf80974436250e9f70ed848836b835b5
git.kernel.org/stable/c/cefa4265b1... WEB
https://git.kernel.org/stable/c/cefa4265b11176c897a7d9e8e54d89e3701c5584

Frequently Asked Questions

What is CVE-2026-64015?
CVE-2026-64015 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition').
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-64015?
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-64015?
CVE-2026-64015 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-64015?
CVE-2026-64015 is classified under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.).
How can I check Maven dependencies for CVE-2026-64015?
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-6rrm-p5j2-8pf8",
  "modified" : "2026-07-20T15:31:55Z",
  "published" : "2026-07-19T18:31:49Z",
  "aliases" : [ "CVE-2026-64015" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsecurity/keys: fix missed RCU read section on lookup\n\nNicholas Carlini reports that the keyring code calls assoc_array_find()\nin find_key_to_update() without holding the RCU read lock, while the\nassoc_array_gc() code really is designed around removing the node from\nthe tree and then freeing it after an RCU grace-period.\n\nThe regular key handling doesn't see this because holding the keyring\nsemaphore hides any lifetime issues, but the persistent key handling\nuses a different model.\n\nInstead of extending the keyring locking, just do the simple RCU locking\nthat the assoc_array was designed for.",
  "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-64015"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/43a1e3744548e6fd85873e6fb43e293eb4010694"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4c5d407ba3ff7f30561ff73ba1b07ed70c864edc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/50bb3435a5e627bfbdc52eb4536f49f88b3486b8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5659e6923cb72f8e18e8b539109ab512455fe195"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/66288dcadf80974436250e9f70ed848836b835b5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cefa4265b11176c897a7d9e8e54d89e3701c5584"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-125", "CWE-362" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-19T16:17:41Z"
  }
}