CVE-2026-98635: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98635 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-98635 at a Glance
How to Fix CVE-2026-98635
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-98635, 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-98635?
Which Software versions are affected?
What version fixes CVE-2026-98635?
What CWE is associated with CVE-2026-98635?
How can I check Maven dependencies for CVE-2026-98635?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-xmm2-hmmq-mgf4",
"modified" : "2026-10-18T18:31:57Z",
"published" : "2026-10-18T18:31:57Z",
"aliases" : [ "CVE-2026-98635" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: block: Fix zones_cond out-of-bounds write on zone report\n\nblk_revalidate_disk_zones() sizes the zones_cond array from the disk\ncapacity and zone size, but the index used by blk_revalidate_zone_cond()\ncomes from the device-driven report_zones() walk and is never checked\nagainst the array size. A device reporting more zones than fit the array\nmakes blk_zone_set_cond() write out of bounds.\n\nOne way to reach this is a zone count exceeding 32 bits: both\nblk_revalidate_zone_args.nr_zones and struct zoned_disk_info.nr_zones are\nunsigned int, so a disk advertising more than UINT_MAX zones (e.g. 2^32 +\n1024 zones of one 512-byte logical block) gets its zone count truncated to\na small value, undersizing the array while the report walk keeps counting\nupward.\n\nCheck the index against the array size before storing the zone condition,\nand refuse to revalidate when the zone count does not fit 32 bits.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98635"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/7c431d61b69a3fd0784c20aa4cd0b8fb501b5653"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/ca688bb207957cffa5a8cad207329b0dcac1f2c0"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:16Z"
}
}