CVE-2026-43439: Software Security Vulnerability Vulnerability
MODERATECVE-2026-43439 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-43439 at a Glance
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).
How to Fix CVE-2026-43439
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:tree
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-43439, 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
References
Frequently Asked Questions
What is CVE-2026-43439?
Which Software versions are affected?
What version fixes CVE-2026-43439?
What is the CVSS score of CVE-2026-43439?
What CWE is associated with CVE-2026-43439?
How can I check Maven dependencies for CVE-2026-43439?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-53qp-89jc-q338",
"modified" : "2026-05-21T18:33:06Z",
"published" : "2026-05-08T15:31:29Z",
"aliases" : [ "CVE-2026-43439" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ncgroup: fix race between task migration and iteration\n\nWhen a task is migrated out of a css_set, cgroup_migrate_add_task()\nfirst moves it from cset->tasks to cset->mg_tasks via:\n\n list_move_tail(&task->cg_list, &cset->mg_tasks);\n\nIf a css_task_iter currently has it->task_pos pointing to this task,\ncss_set_move_task() calls css_task_iter_skip() to keep the iterator\nvalid. However, since the task has already been moved to ->mg_tasks,\nthe iterator is advanced relative to the mg_tasks list instead of the\noriginal tasks list. As a result, remaining tasks on cset->tasks, as\nwell as tasks queued on cset->mg_tasks, can be skipped by iteration.\n\nFix this by calling css_set_skip_task_iters() before unlinking\ntask->cg_list from cset->tasks. This advances all active iterators to\nthe next task on cset->tasks, so iteration continues correctly even\nwhen a task is concurrently being migrated.\n\nThis race is hard to hit in practice without instrumentation, but it\ncan be reproduced by artificially slowing down cgroup_procs_show().\nFor example, on an Android device a temporary\n/sys/kernel/cgroup/cgroup_test knob can be added to inject a delay\ninto cgroup_procs_show(), and then:\n\n 1) Spawn three long-running tasks (PIDs 101, 102, 103).\n 2) Create a test cgroup and move the tasks into it.\n 3) Enable a large delay via /sys/kernel/cgroup/cgroup_test.\n 4) In one shell, read cgroup.procs from the test cgroup.\n 5) Within the delay window, in another shell migrate PID 102 by\n writing it to a different cgroup.procs file.\n\nUnder this setup, cgroup.procs can intermittently show only PID 101\nwhile skipping PID 103. Once the migration completes, reading the\nfile again shows all tasks as expected.\n\nNote that this change does not allow removing the existing\ncss_set_skip_task_iters() call in css_set_move_task(). The new call\nin cgroup_migrate_add_task() only handles iterators that are racing\nwith migration while the task is still on cset->tasks. Iterators may\nalso start after the task has been moved to cset->mg_tasks. If we\ndropped css_set_skip_task_iters() from css_set_move_task(), such\niterators could keep task_pos pointing to a migrating task, causing\ncss_task_iter_advance() to malfunction on the destination css_set,\nup to and including crashes or infinite loops.\n\nThe race window between migration and iteration is very small, and\ncss_task_iter is not on a hot path. In the worst case, when an\niterator is positioned on the first thread of the migrating process,\ncgroup_migrate_add_task() may have to skip multiple tasks via\ncss_set_skip_task_iters(). However, this only happens when migration\nand iteration actually race, so the performance impact is negligible\ncompared to the correctness fix provided here.",
"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-43439"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/3b95abab7369235a37b15eaec6e1a0b443bba7c7"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/3dfd1328c05234e8d8fa61948b2ba82680594988"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/4a9654a2b46cfdaae287fb8995f536245635e467"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/5ee01f1a7343d6a3547b6802ca2d4cdce0edacb1"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/7c85debc35e6d131bd29c64f2ae78c6ede0e55c4"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/86ceaccfdfa16dad05addb33dc206e03589bcfd1"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9cca530c7cc1b3e02cb8fa7f80060dd4b38562ce"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9dc76f6fc0d28d2382583715bc4ec22f28104845"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-362" ],
"severity" : "MODERATE",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-05-08T15:16:56Z"
}
}