CVE-2026-98664: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98664 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-98664 at a Glance
How to Fix CVE-2026-98664
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-98664, 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-98664?
Which Software versions are affected?
What version fixes CVE-2026-98664?
What CWE is associated with CVE-2026-98664?
How can I check Maven dependencies for CVE-2026-98664?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-w4fg-xq8w-gq57",
"modified" : "2026-10-18T18:31:58Z",
"published" : "2026-10-18T18:31:58Z",
"aliases" : [ "CVE-2026-98664" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\niio: imu: adis16400: fix unprotected debugfs reads\n\nadis16400_serial_number_fops is open coded and never calls\ndebugfs_file_get(), so debugfs_remove_recursive() does not wait for a\nread in progress and unbind frees the iio_dev underneath it.\n\nCommit ae1d37a9bb4b (\"iio: imu: adis16400: use DEFINE_DEBUGFS_ATTRIBUTE\ninstead of DEFINE_SIMPLE_ATTRIBUTE\") converted product_id and\nflash_count to DEFINE_DEBUGFS_ATTRIBUTE, which protects itself, but\nmoved all three files to debugfs_create_file_unsafe().\n\nserial_number prints three registers as \"%.4x-%.4x-%.4x\" and\nDEFINE_DEBUGFS_ATTRIBUTE() formats a single u64, so it cannot be\nconverted without changing what the file returns. adis16475 and\nadis16550 already use debugfs_create_file() for their open coded\nfiles. Use it here too.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98664"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/50e8d70ba0743f88afd7e49f9cebd1841ee677f5"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/d94787287a113a1326211647d5e0deed1e9de105"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/e9b4c00f775a915b759b08bfe2c5e806a8301a59"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/f501302ebb9e1504162351b951fe3ae331c852ab"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:19Z"
}
}