CVE-2026-98418: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98418 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-98418 at a Glance
How to Fix CVE-2026-98418
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-98418, 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-98418?
Which Software versions are affected?
What version fixes CVE-2026-98418?
What CWE is associated with CVE-2026-98418?
How can I check Maven dependencies for CVE-2026-98418?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-2pjr-w693-xmqc",
"modified" : "2026-10-14T15:32:21Z",
"published" : "2026-10-14T15:32:21Z",
"aliases" : [ "CVE-2026-98418" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsched/core: Avoid false migration warning for proxy donors\n\nProxy execution can move a blocked donor's scheduling context to the\nlock owner's CPU even when the donor is migration-disabled. The donor\ndoes not execute there, and its original execution CPU remains recorded\nin wake_cpu.\n\nset_task_cpu() warns unconditionally for migration-disabled tasks, so a\nsubsequent proxy migration or the wakeup path returning the donor home\ntriggers a false positive: moving a blocked scheduling context does not\nviolate the migration-disabled execution context.\n\nFor example, creating a mutex owner on CPU1 and a migration-disabled\nwaiter on CPU0 can trigger the following warning:\n\n proxy_migrate_repro: donor blocking on CPU0 with migration disabled\n proxy_migrate_repro: donor moved from CPU0 to CPU1\n WARNING: kernel/sched/core.c:3389 at set_task_cpu+0x1d3/0x280\n ...\n Call Trace:\n try_to_wake_up+0x43f/0x780\n __mutex_unlock_slowpath+0x330/0x540\n owner_fn+0x9f/0xc0 [proxy_migrate_repro]\n ...\n proxy_migrate_repro: donor woke on CPU0, task_cpu=0\n proxy_migrate_repro: completed\n\nExclude blocked proxy donors from the warning. The proxy wakeup path\nrestores an executable placement before clearing the blocked state.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98418"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/e4a442da49fff7619b3cb2988e477022dcea6688"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/fe3c73d7bc769e7afc252f867a3421fe168b898d"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-14T14:17:53Z"
}
}