CVE-2026-46316: Software Security Vulnerability Vulnerability
CRITICALCVE-2026-46316 is a CRITICAL (CVSS 9.3) 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-46316 at a Glance
Security Impact
CVSS: 9.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).
How to Fix CVE-2026-46316
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:treeHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-46316, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:treeAnalyze 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
References
Frequently Asked Questions
What is CVE-2026-46316?
Which Software versions are affected?
What version fixes CVE-2026-46316?
What is the CVSS score of CVE-2026-46316?
What CWE is associated with CVE-2026-46316?
How can I check Maven dependencies for CVE-2026-46316?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-qcxh-2cm7-9fcc",
"modified" : "2026-07-30T12:32:09Z",
"published" : "2026-06-09T15:32:17Z",
"aliases" : [ "CVE-2026-46316" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry\n\nvgic_its_invalidate_cache() walks the per-ITS translation cache with\nxa_for_each() and drops the cache's reference on each entry with\nvgic_put_irq(). It puts the iterated pointer, though, rather than the\nvalue returned by xa_erase().\n\nThe function is called from contexts that do not exclude one another: the\nITS command handlers hold its_lock, the GITS_CTLR write path holds\ncmd_lock, and the path that clears EnableLPIs in a redistributor's\nGICR_CTLR holds neither. Two or more of them can drain the same cache\nconcurrently, and if each one observes the same entry, erases it and then\nputs it, the single reference the cache holds on that entry is dropped\nmore than once. The entry can then be freed while an ITE still maps it.\n\nxa_erase() is atomic and returns the previous entry, so put only the entry\nthat this context actually removed. The cache reference is then dropped\nexactly once per entry even when the invalidations run concurrently, and\nthe behavior is unchanged when only one context runs.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H"
} ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46316"
}, {
"type" : "WEB",
"url" : "https://access.redhat.com/errata/RHSA-2026:34911"
}, {
"type" : "WEB",
"url" : "https://access.redhat.com/errata/RHSA-2026:36018"
}, {
"type" : "WEB",
"url" : "https://access.redhat.com/errata/RHSA-2026:38902"
}, {
"type" : "WEB",
"url" : "https://access.redhat.com/errata/RHSA-2026:39371"
}, {
"type" : "WEB",
"url" : "https://access.redhat.com/errata/RHSA-2026:40764"
}, {
"type" : "WEB",
"url" : "https://access.redhat.com/errata/RHSA-2026:40779"
}, {
"type" : "WEB",
"url" : "https://access.redhat.com/errata/RHSA-2026:40787"
}, {
"type" : "WEB",
"url" : "https://access.redhat.com/errata/RHSA-2026:44231"
}, {
"type" : "WEB",
"url" : "https://access.redhat.com/security/cve/CVE-2026-46316"
}, {
"type" : "WEB",
"url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2486982"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/13031fb6b8357fbbcded2a7f4cba73e4781ee594"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/2bbc395e81bd29c543a0529a678327e932a7ec69"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9121f4605ab94969f62d1b5714ca3c6c69bd202f"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/b7b72e88046328c9fdc638fe887d4240257dd5dc"
}, {
"type" : "WEB",
"url" : "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-46316.json"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-362", "CWE-911" ],
"severity" : "CRITICAL",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-06-09T13:16:36Z"
}
}