CVE-2026-97432: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-97432 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-97432 at a Glance
How to Fix CVE-2026-97432
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-97432, 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-97432?
Which Software versions are affected?
What version fixes CVE-2026-97432?
What CWE is associated with CVE-2026-97432?
How can I check Maven dependencies for CVE-2026-97432?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-w9g9-vhwv-w598",
"modified" : "2026-09-24T18:31:32Z",
"published" : "2026-09-24T18:31:32Z",
"aliases" : [ "CVE-2026-97432" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: fix P2P-Device binding handling\n\nOur binding handling for P2P-Device can run into the following\nscenario, as observed by our testing:\n\n - a station interface is connected on some channel\n - the P2P-Device does a remain-on-channel (ROC) on that channel\n - the ROC ends, and the P2P-Device is removed from the binding,\n but the phy_ctxt pointer is left around as a PHY cache so we\n don't need to recalibrate to the channel again and again in\n case it's not shared\n - a binding update by the station interface, even a removal,\n will re-add the P2P-Device to the binding\n - the P2P-Device is removed, which removes the PHY context, but\n it's still in the binding so the firmware crashes\n\nSince the P2P device is removed from the binding and only re-\nadded by unrelated code, but we want to keep the phy_ctxt around\nas a cache for future ROC usage, fix it by adding a boolean that\nindicates whether or not the P2P-Device should be added to the\nbinding, and handle that in the binding iterator. That way, the\nstation interface cannot re-add the P2P-Device to the binding\nwhen that isn't active.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97432"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/7be2fc679c8f657868988e41c0bb15bf5a454620"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/b74e377cad9271950c57472867c469e4b5b2ff0c"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-24T17:17:21Z"
}
}