CVE-2026-90079: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-90079 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-90079 at a Glance
How to Fix CVE-2026-90079
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-90079, 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-90079?
Which Software versions are affected?
What version fixes CVE-2026-90079?
What CWE is associated with CVE-2026-90079?
How can I check Maven dependencies for CVE-2026-90079?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-g2m5-qf5x-2p4w",
"modified" : "2026-10-15T12:30:47Z",
"published" : "2026-09-17T18:31:49Z",
"aliases" : [ "CVE-2026-90079" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nocteontx2-af: fix cn20k mailbox lifetime on repeated rvu_mbox_init()\n\nrvu_mbox_init() is called separately for AF-PF mailboxes during probe\nand for AF-VF mailboxes when SR-IOV is enabled. Each call used to\nallocate a new ng_rvu object, leaking the first allocation when the\npointer was overwritten on the second call.\n\nSharing one ng_rvu across both paths exposed several teardown bugs:\nthe error path freed all cn20k mailbox DMA and kfree()d ng_rvu even\nwhen only the failing init type should be unwound, leaving live AF-PF\nmailbox memory in use after an AF-VF init failure. mutex_init() was\nalso re-run on the AF-VF path while AF-PF mailbox handlers could still\nhold rvu->mbox_lock. Probe and SR-IOV failure paths did not release\ncn20k mailbox DMA either, since cleanup only happened in rvu_remove().\n\nAllocate ng_rvu once with devm_kzalloc(), initialize mbox_lock in the\nsame block, unwind only the mailbox memory for the failing init type,\nand free cn20k mailbox DMA from the probe and pci_enable_sriov()\nerror paths.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90079"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/3b11a77f69980932c3924054d66e565c9a135747"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/a0fcbea79f034f49bdd44915f28938922023458d"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/c08314f91782983d67af0807ed1360e404ac4a8b"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-17T17:16:57Z"
}
}