CVE-2026-98866: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98866 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.
CVE-2026-98866 at a Glance
How to Fix CVE-2026-98866
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-98866, 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 General Security Weakness. 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-98866?
Which Software versions are affected?
What version fixes CVE-2026-98866?
What CWE is associated with CVE-2026-98866?
How can I check Maven dependencies for CVE-2026-98866?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-3r69-998r-q4c2",
"modified" : "2026-10-18T18:32:06Z",
"published" : "2026-10-18T18:32:06Z",
"aliases" : [ "CVE-2026-98866" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsched/cache: Introduce task_struct->sched_cache_grp to fix UAF\n\nAdd a sched_cache_grp pointer to task_struct so that scheduler code\ncan access the cache group directly via the task, without going\nthrough mm->sched_cache_grp. This decouples the scheduler's hot-path\naccesses from the mm_struct.\n\nEach task holds its own refcount on the sched_cache_group, separate\nfrom the reference held by its mm_struct. The reference is acquired\nin copy_mm() (fork) and exec_mmap() (exec), and released in exit_mm().\nThis fixes the use-after-free when account_mm_sched() reaches the group\nthrough a task whose mm is being switched, as reported by Hyunwoo:\n\n https://lore.kernel.org/lkml/apPb-Dr4nPYuHQOK@v4bel/\n\nConvert all scheduler code in fair.c and exit.c to use\np->sched_cache_grp instead of p->mm->sched_cache_grp.\n\nKeep the fork/exec/exit reference management out of the generic mm\npaths: add sched_cache_fork(), sched_cache_fork_cleanup(),\nsched_cache_exec_mmap() and sched_cache_exit_mm() in\nkernel/sched/cache_sched.c (with empty stubs for !CONFIG_SCHED_CACHE),\nso fs/exec.c, kernel/fork.c and kernel/exit.c each call one helper\ninstead of open-coding the refcounting under #ifdef. Also add\nsched_cache_group_get() and task_cache_group_get().",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98866"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9436130e6da72af63289a4acb3aa0c1df07a3928"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/b636fef85bda7d1bab9c0a45067ab1508d79d946"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:41Z"
}
}