CVE-2026-64043: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-74fm-4xxg-774p
CVSS 4.7
CWE-362
Published
Advisory Summary

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

CVE Identifier CVE-2026-64043
GHSA Identifier GHSA-74fm-4xxg-774p
Severity MODERATE
CVSS v3.1 Base Score 4.7
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: 4.7

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

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
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-64043

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-64043, 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: ovpn: fix race between deleting interface and adding new peer While deleting an existing ovpn interface, there is a very narrow window where adding a new peer via netlink may cause the netdevice to hang and prevent its unregistration. It may happen during ovpn_dellink(), when all existing peers are freed and the device is queued for deregistration, but a CMD_PEER_NEW message comes in adding a new peer that takes again a reference to the netdev. At this point there is no way to release the device because we are under the assumption that all peers were already released. Fix the race condition by releasing all peers in ndo_uninit(), when the netdevice has already been removed from the netdev list. Also ovpn_peer_add() has now an extra check that forces the function to bail out if the device reg_state is not REGISTERED. This way any incoming CMD_PEER_NEW racing with the interface deletion routine will simply stop before adding the peer. Note that the above check happens while holding the netdev_lock to prevent racing netdev state changes. ovpn_dellink() is now empty and can be removed.

References

Frequently Asked Questions

What is CVE-2026-64043?
CVE-2026-64043 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-64043?
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-64043?
CVE-2026-64043 has a CVSS v3.1 base score of 4.7 (MODERATE) with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-64043?
CVE-2026-64043 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-64043?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-74fm-4xxg-774p",
  "modified" : "2026-10-05T18:34:11Z",
  "published" : "2026-07-19T18:31:50Z",
  "aliases" : [ "CVE-2026-64043" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\novpn: fix race between deleting interface and adding new peer\n\nWhile deleting an existing ovpn interface, there is a very\nnarrow window where adding a new peer via netlink may cause\nthe netdevice to hang and prevent its unregistration.\n\nIt may happen during ovpn_dellink(), when all existing peers are\nfreed and the device is queued for deregistration, but a\nCMD_PEER_NEW message comes in adding a new peer that takes again\na reference to the netdev.\n\nAt this point there is no way to release the device because we are\nunder the assumption that all peers were already released.\n\nFix the race condition by releasing all peers in ndo_uninit(),\nwhen the netdevice has already been removed from the netdev\nlist.\n\nAlso ovpn_peer_add() has now an extra check that forces the\nfunction to bail out if the device reg_state is not REGISTERED.\nThis way any incoming CMD_PEER_NEW racing with the interface\ndeletion routine will simply stop before adding the peer.\n\nNote that the above check happens while holding the netdev_lock\nto prevent racing netdev state changes.\n\novpn_dellink() is now empty and can be removed.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/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-64043"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/097d62df38314c14b88fab9096f3461baf158e2b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/982422b11e6f95f766a8cd2c2b1cbdb77e234a61"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/de9fec2a6645f5b4d23398cd870a33e2703728d9"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-362" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-19T16:17:44Z"
  }
}