CVE-2026-89529: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-89529 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-89529 at a Glance
How to Fix CVE-2026-89529
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-89529, 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-89529?
Which Software versions are affected?
What version fixes CVE-2026-89529?
What CWE is associated with CVE-2026-89529?
How can I check Maven dependencies for CVE-2026-89529?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-4fgg-mw2q-x784",
"modified" : "2026-09-11T21:31:30Z",
"published" : "2026-09-11T21:31:30Z",
"aliases" : [ "CVE-2026-89529" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: Reject oversized Read segments at decode time\n\nThe RPC/RDMA Read list decoder stores wire-supplied segment\nlengths without validation. xdr_count_read_segments() checks\n4-byte alignment for non-zero position values but does not\ncap the segment length.\n\nAn oversized rs_length reaches svc_rdma_build_read_segment(),\nwhich derives nr_bvec from it and can drive a large dynamic\nbvec allocation before verifying that enough rq_pages remain.\nIf the post-allocation page-overrun guard fires, the freshly\nacquired rw context is not returned, leaking the resource.\n\nReject any segment whose length exceeds the receive context's\npage budget during Read list decoding, consistent with how\nxdr_check_write_chunk() bounds Write segment counts against\nrc_maxpages. Also return the rw context on the existing\npost-allocation overrun path in svc_rdma_build_read_segment(),\nkeeping that defensive guard balanced.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89529"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/5120fe54e0e2f5b62797a432115cc61d61117a5b"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/af6f0e06bed818ee7fc8b869915964410020a1c5"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-11T20:19:35Z"
}
}