CVE-2026-89725: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-946x-47hf-5c7p
CVSS 8.8
Published
Advisory Summary

CVE-2026-89725 is a HIGH (CVSS 8.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-89725 at a Glance

CVE Identifier CVE-2026-89725
GHSA Identifier GHSA-946x-47hf-5c7p
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.8

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

Attack Vector Adjacent (AV:A)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
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-89725

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-89725, 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: media: cec: stm32: prevent out-of-bounds write on RX overflow stm32_rx_done() appends each received CEC byte to rx_msg.msg[] using rx_msg.len as the write index, incrementing it on every RXBR (receive-byte-ready) interrupt without checking it against the buffer size: cec->rx_msg.msg[cec->rx_msg.len++] = val & 0xFF; rx_msg.msg[] is a fixed CEC_MAX_MSG_SIZE (16) byte array in struct cec_msg, and rx_msg.len is only reset on RXACKE/RXOVR or after a completed message (RXEND). The number of bytes received before RXEND is decided by the remote CEC device (it sets EOM), not by the driver. A peer that keeps sending bytes without ending the message drives RXBR repeatedly, pushing rx_msg.len past 16 and writing peer-controlled bytes out of bounds into the surrounding memory. This is reachable in normal operation once the driver has probed and receiving is enabled, from the IRQ thread, without any local privilege. The length check in the CEC core runs on the consumer side, after the byte has been stored, so it does not prevent the overflow. Bound the index in the driver before the store, as the other platform CEC drivers already do (e.g. tegra_cec), dropping the excess bytes of an overlong frame. Found by static analysis tool CodeQL.

References

Frequently Asked Questions

What is CVE-2026-89725?
CVE-2026-89725 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-89725?
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-89725?
CVE-2026-89725 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-89725?
CVE-2026-89725 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89725?
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-946x-47hf-5c7p",
  "modified" : "2026-09-14T15:32:35Z",
  "published" : "2026-09-11T21:31:38Z",
  "aliases" : [ "CVE-2026-89725" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: cec: stm32: prevent out-of-bounds write on RX overflow\n\nstm32_rx_done() appends each received CEC byte to rx_msg.msg[] using\nrx_msg.len as the write index, incrementing it on every RXBR\n(receive-byte-ready) interrupt without checking it against the buffer\nsize:\n\n\tcec->rx_msg.msg[cec->rx_msg.len++] = val & 0xFF;\n\nrx_msg.msg[] is a fixed CEC_MAX_MSG_SIZE (16) byte array in struct\ncec_msg, and rx_msg.len is only reset on RXACKE/RXOVR or after a\ncompleted message (RXEND). The number of bytes received before RXEND is\ndecided by the remote CEC device (it sets EOM), not by the driver. A\npeer that keeps sending bytes without ending the message drives RXBR\nrepeatedly, pushing rx_msg.len past 16 and writing peer-controlled bytes\nout of bounds into the surrounding memory. This is reachable in normal\noperation once the driver has probed and receiving is enabled, from the\nIRQ thread, without any local privilege.\n\nThe length check in the CEC core runs on the consumer side, after the\nbyte has been stored, so it does not prevent the overflow. Bound the\nindex in the driver before the store, as the other platform CEC drivers\nalready do (e.g. tegra_cec), dropping the excess bytes of an overlong\nframe.\n\nFound by static analysis tool CodeQL.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89725"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0c260d3f97e52978a8c769bb095ac0901333a3ac"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1b4fdefd788db990d1805feb5c7b2388de791ecd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/37ac45f7d6e3a6a5dcf6452a0b7bad9a543e8344"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3df1a4026662121011187247897fe95fd84e8a3a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a85ce3b175615c2e13bc01e8a1b6b6b6910fde57"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c3edd7fb8e3692423a702705509947fc9c30b3d1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f2499b720ea9b874d58770885c6c2e8445a8c3ef"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fb9dda38d4b9e90db07ed9a0ee2d35bf85494035"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:20:02Z"
  }
}