CVE-2026-90432: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-90432 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-90432 at a Glance
How to Fix CVE-2026-90432
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-90432, 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-90432?
Which Software versions are affected?
What version fixes CVE-2026-90432?
What CWE is associated with CVE-2026-90432?
How can I check Maven dependencies for CVE-2026-90432?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-3xgc-q8gm-m2rg",
"modified" : "2026-09-17T18:32:05Z",
"published" : "2026-09-17T18:32:05Z",
"aliases" : [ "CVE-2026-90432" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Abort directly from the hardlockup handler\n\nscx_hardlockup() defers the abort to an irq_work because exit claiming used\nto take scx_sched_lock and couldn't run from NMI. The deferral is now\nunnecessary - claiming is NMI-safe and asserting ->aborting is exactly what\nbreaks the live-locks that hard-lock CPUs. Call handle_lockup() directly and\ndrop the irq_work. This also makes the self-detected case recoverable: the\nperf watchdog fires on the hard-locked CPU itself, where a queued irq_work\nnever runs with IRQs off.\n\nAlso fix the return value: %true used to be returned whenever sched_ext was\nloaded, suppressing the kernel's hardlockup report even when the abort was\nrefused. Return %true only when this call initiated the abort.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90432"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/3c4b38064937a761ebbf85b1649e812db85eb59e"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/4d6270bbb4e083a4d2d39f3c36f30f5c939c06ed"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-17T17:17:48Z"
}
}