CVE-2026-89519: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-89519 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-89519 at a Glance
How to Fix CVE-2026-89519
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-89519, 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-89519?
Which Software versions are affected?
What version fixes CVE-2026-89519?
What CWE is associated with CVE-2026-89519?
How can I check Maven dependencies for CVE-2026-89519?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-4vmj-w324-pvrj",
"modified" : "2026-09-11T21:31:30Z",
"published" : "2026-09-11T21:31:30Z",
"aliases" : [ "CVE-2026-89519" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Replace SCX_RQ_BAL_KEEP with a dispatch verdict return\n\nSCX_RQ_BAL_KEEP tells the pick to keep running the previous task, a leftover\nfrom when balancing and picking were separate operations. An rq-level flag\nonly works while dispatches and picks pair up one to one, which core\nscheduling breaks: selections interleave through dispatch's lock drops and a\npick can consume a stale flag, keeping a task that has since been dequeued.\nFixing core scheduling support requires the decision to travel with the\ndispatch that made it. Make scx_dispatch_sched() and balance_one() return an\nexplicit verdict instead and drop the flag's plumbing from the tools autogen\nenum headers.\n\nAlso factor the pick-side invocation, its follow-up queueing and the\npost-dispatch checks out of do_pick_task_scx() into dispatch_pick(). No\nfunctional changes intended.\n\nv2: Drop the SCX_RQ_BAL_KEEP plumbing from the tools autogen enum headers\n as well (Andrea).",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89519"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/6f1d3bfe54430f8d54e0530a27f2ecbf8466576e"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/ffaab58d217581cb75353168f8812a16e10463fc"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-11T20:19:34Z"
}
}