CVE-2026-89620: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-w336-hgqx-wc5g
CVSS 7.8
Published
Advisory Summary

CVE-2026-89620 is a HIGH (CVSS 7.8) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-89620 at a Glance

CVE Identifier CVE-2026-89620
GHSA Identifier GHSA-w336-hgqx-wc5g
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-89620

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-89620, 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: HID: intel-thc-hid: intel-quickspi: validate report size before copy write_cmd_to_txdma() builds an output report in qsdev->report_buf, a heap buffer allocated in quickspi_alloc_report_buf() to the device-descriptor derived max_report_len (a few hundred bytes for a touch controller). It copies the caller-supplied report into that buffer: memcpy(write_buf->content, report_buf, report_buf_len); The HID core caps a report at HID_MAX_BUFFER_SIZE (16384) by default, and quickspi_hid_ll_driver does not set max_buffer_size, so the length reaches the driver unbounded. A hidraw SET_REPORT/SET_FEATURE ioctl carrying a report larger than max_report_len therefore overflows report_buf with attacker-controlled length and content. Record the report_buf allocation size and reject reports that do not fit before copying, matching the equivalent guard in the intel-quicki2c sibling (quicki2c_init_write_buf()) and the hid-goodix-spi fix. write_cmd_to_txdma() writes the output report header ahead of the content in the same buffer, so size the allocation to cover the header as well. That keeps the added bound from rejecting a maximum-sized report.

References

Frequently Asked Questions

What is CVE-2026-89620?
CVE-2026-89620 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-89620?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-89620?
CVE-2026-89620 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-89620?
CVE-2026-89620 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89620?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-w336-hgqx-wc5g",
  "modified" : "2026-09-13T09:32:24Z",
  "published" : "2026-09-11T21:31:34Z",
  "aliases" : [ "CVE-2026-89620" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: intel-thc-hid: intel-quickspi: validate report size before copy\n\nwrite_cmd_to_txdma() builds an output report in qsdev->report_buf, a heap\nbuffer allocated in quickspi_alloc_report_buf() to the device-descriptor\nderived max_report_len (a few hundred bytes for a touch controller).  It\ncopies the caller-supplied report into that buffer:\n\n    memcpy(write_buf->content, report_buf, report_buf_len);\n\nThe HID core caps a report at HID_MAX_BUFFER_SIZE (16384) by default, and\nquickspi_hid_ll_driver does not set max_buffer_size, so the length reaches\nthe driver unbounded.  A hidraw SET_REPORT/SET_FEATURE ioctl carrying a\nreport larger than max_report_len therefore overflows report_buf with\nattacker-controlled length and content.\n\nRecord the report_buf allocation size and reject reports that do not fit\nbefore copying, matching the equivalent guard in the intel-quicki2c\nsibling (quicki2c_init_write_buf()) and the hid-goodix-spi fix.\n\nwrite_cmd_to_txdma() writes the output report header ahead of the content\nin the same buffer, so size the allocation to cover the header as well.\nThat keeps the added bound from rejecting a maximum-sized report.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89620"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6fcefe71aeb524f6e77fe586fe85d873745e917c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a59cf84441f9a17323c89452cec2bf16724c48a9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ee8ad1bb1e96164d51089b1182f1bd5f187e7baa"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:47Z"
  }
}