CVE-2026-98786: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98786 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-98786 at a Glance
How to Fix CVE-2026-98786
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-98786, 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-98786?
Which Software versions are affected?
What version fixes CVE-2026-98786?
What CWE is associated with CVE-2026-98786?
How can I check Maven dependencies for CVE-2026-98786?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-7r8j-xcf8-cxq6",
"modified" : "2026-10-18T18:32:03Z",
"published" : "2026-10-18T18:32:03Z",
"aliases" : [ "CVE-2026-98786" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: guard dc_sink dereferences in MST mode validation\n\ndm_dp_mst_is_port_support_mode() reads\naconnector->dc_sink->dsc_caps... for the DSC branch-throughput check,\nand get_conv_frl_bw()'s HDMI-PCON FRL-bandwidth path reads\naconnector->dc_sink->edid_caps.max_frl_rate, both without a NULL\ncheck. dc_sink is cleared asynchronously on MST unplug, and both\nfunctions run from paths that the driver's own comments document as\nracing that teardown: the connector probe worker's ->mode_valid\ncallback and a compositor's atomic check, neither of which holds the\nMST manager lock that the teardown path uses. The former does have an\nexisting dsc_aux NULL check, but dsc_aux isn't reliably cleared in\nevery path that clears dc_sink, so it doesn't cover this.\n\nFail the port-support check and skip the FRL conversion path when the\nsink is already gone.\n\n(cherry picked from commit 7c3db8da4e039698ae198c870712428644e965c7)",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98786"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/217f64f348c90cba62164e7ff38e0ccf78a5ca09"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/daa0437fe5e451856aaf8fda602a9fc2105bbd54"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:32Z"
}
}