CVE-2026-98779: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98779 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-98779 at a Glance
How to Fix CVE-2026-98779
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-98779, 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-98779?
Which Software versions are affected?
What version fixes CVE-2026-98779?
What CWE is associated with CVE-2026-98779?
How can I check Maven dependencies for CVE-2026-98779?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-7q7p-f6vv-qrwf",
"modified" : "2026-10-18T18:32:03Z",
"published" : "2026-10-18T18:32:03Z",
"aliases" : [ "CVE-2026-98779" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix ACP MFD device leak on init failure\n\nacp_hw_init() registers ACP child devices with mfd_add_devices() before\nattaching them to the ACP power domain and initializing the hardware.\n\nIf attaching a child to the power domain fails, or if the ACP reset or\nclock enable operation times out, the failure path frees only the\nsource cell, resource, and platform-data allocations. The child\nplatform devices already registered by mfd_add_devices() remain\nregistered and are never released.\n\nRemove the children from the power domain and unregister the MFD\ndevices on failures that occur after mfd_add_devices() succeeds. Keep\nmfd_add_devices() failures on the existing cleanup path since the MFD\ncore already rolls back partially registered children itself.\n\nThe issue was identified by a static analysis tool I developed and\nconfirmed by manual review.\n\n(cherry picked from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560)",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98779"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/2b9a53940a2bc063ea4cd09ee49220a503a0170c"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/587469076e4ffb617f7ad1a0c4a13072a3e87113"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/abf854513bc19e6e24d45353ac99ec5627ee0acc"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/f0013046151b7467e62c471c1c83d63ea255799c"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:31Z"
}
}