CVE-2026-98711: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-rfqv-xwf2-63qv
Share
Published
Advisory Summary

CVE-2026-98711 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-98711 at a Glance

CVE Identifier CVE-2026-98711
GHSA Identifier GHSA-rfqv-xwf2-63qv
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98711

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.

Verify Direct and Transitive Dependencies

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-98711, 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

In the Linux kernel, the following vulnerability has been resolved: wifi: cw1200: fix TX padding OOB read leaking heap data to device The TX path rounds the transfer size up to the bus alignment (align_size(), up to 511 bytes for SDIO, 1 byte for SPI) but sends the padded length straight from the frame buffer, which has no room reserved for the padding. cw1200_data_write() therefore reads past the end of the frame and the bus transfer carries those bytes to the device. A bogus device can collect up to 511 bytes of kernel heap data per TX frame. The RX path does not have this problem: it allocates the skb with the aligned length (alloc_len) before reading. Compute the exact padding with the bus align_size() callback, make sure queued TX frames have tailroom for it, and zero the padding bytes before the transfer so nothing past the frame is exposed. This is not expected to change driver behavior on most cases: frame contents and transfer sizes are unchanged, only the content of the padding bytes (previously undefined stale memory, now zero), which the device never reads since the WSM header carries the real frame length. The skb expansion can only fail under memory exhaustion, in which case the frame is dropped like on the existing error paths of cw1200_tx(). Discovered by Atuin - Automated Vulnerability Discovery Engine.

References

NVD — CVE-2026-98711 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98711
git.kernel.org/stable/c/678c8f4ba2... WEB
https://git.kernel.org/stable/c/678c8f4ba285649d5418a858d5d4f30c728a54ad
git.kernel.org/stable/c/71f693a0ec... WEB
https://git.kernel.org/stable/c/71f693a0ecccf36532dd2790f7969da6c71d5d23
git.kernel.org/stable/c/7c16117808... WEB
https://git.kernel.org/stable/c/7c1611780823b76219cb1478db53dfd890c4a9a2
git.kernel.org/stable/c/b0e97bd40e... WEB
https://git.kernel.org/stable/c/b0e97bd40e0c2cb1a3530ef8f6250aacf3224515

Frequently Asked Questions

What is CVE-2026-98711?
CVE-2026-98711 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98711?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98711?
CVE-2026-98711 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98711?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rfqv-xwf2-63qv",
  "modified" : "2026-10-18T18:32:00Z",
  "published" : "2026-10-18T18:32:00Z",
  "aliases" : [ "CVE-2026-98711" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: cw1200: fix TX padding OOB read leaking heap data to device\n\nThe TX path rounds the transfer size up to the bus alignment\n(align_size(), up to 511 bytes for SDIO, 1 byte for SPI) but sends\nthe padded length straight from the frame buffer, which has no room\nreserved for the padding.  cw1200_data_write() therefore reads past\nthe end of the frame and the bus transfer carries those bytes to the\ndevice.  A bogus device can collect up to 511 bytes of kernel heap\ndata per TX frame.\n\nThe RX path does not have this problem: it allocates the skb with\nthe aligned length (alloc_len) before reading.\n\nCompute the exact padding with the bus align_size() callback, make\nsure queued TX frames have tailroom for it, and zero the padding\nbytes before the transfer so nothing past the frame is exposed.\n\nThis is not expected to change driver behavior on most cases: frame\ncontents and transfer sizes are unchanged, only the content of the\npadding bytes (previously undefined stale memory, now zero), which\nthe device never reads since the WSM header carries the real frame\nlength.  The skb expansion can only fail under memory exhaustion,\nin which case the frame is dropped like on the existing error paths\nof cw1200_tx().\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98711"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/678c8f4ba285649d5418a858d5d4f30c728a54ad"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/71f693a0ecccf36532dd2790f7969da6c71d5d23"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7c1611780823b76219cb1478db53dfd890c4a9a2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b0e97bd40e0c2cb1a3530ef8f6250aacf3224515"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:24Z"
  }
}