CVE-2026-89557: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-233m-c5r9-wq53
Share
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-89557
GHSA Identifier GHSA-233m-c5r9-wq53
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-89557

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-89557, 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: md: do overflow check for sb->bblog_shift in super_1_load() In super_1_load(), sb->bblog_shift is an __u8 type value loaded from on- disk superblock. It is used for badblocks API badblocks_set() by the following sequence, 1930 rdev->badblocks.shift = sb->bblog_shift; 1931 for (i = 0 ; i < (sectors << (9-3)) ; i++, bbp++) { 1932 u64 bb = le64_to_cpu(*bbp); 1933 int count = bb & (0x3ff); 1934 u64 sector = bb >> 10; 1935 sector <<= sb->bblog_shift; 1936 count <<= sb->bblog_shift; 1937 if (bb + 1 == 0) 1938 break; 1939 if (!badblocks_set(&rdev->badblocks, sector, count, 1)) 1940 return -EINVAL; 1941 } bb->bblog_shit is in range of 0-255, variable sector is 64bit width, for an invalid bb->bblog_shit, it is possible to make sector be overflowed by the following calculation, 1935 sector <<= sb->bblog_shift; Then in turn when call badblocks_set() at line 1939 with the invalid rdev->badblocks.shift set at line 1930, may result an overflow inside _badblocks_clear() in block/badblocks.c. Although there are many places to call badblocks APIs, the non-zero shift value is only used in super_1_load(), other places always use 0 as the shift value. Therefore it is unnecessary to do a general shift value overflow check inside badblock API, and just check here as the caller. This may avoid unnecessary check, make the badblocks API code more simple and elegant.

References

NVD — CVE-2026-89557 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89557
git.kernel.org/stable/c/0a03f9541c... WEB
https://git.kernel.org/stable/c/0a03f9541c06fda64301dcf94f376f07ce2cc396
git.kernel.org/stable/c/323f3a056d... WEB
https://git.kernel.org/stable/c/323f3a056dbccb39a642ebde642044a680f3a6d6
git.kernel.org/stable/c/35d522bd32... WEB
https://git.kernel.org/stable/c/35d522bd32462afcf1981dab6da8a9256c26c1e0
git.kernel.org/stable/c/3b097416b4... WEB
https://git.kernel.org/stable/c/3b097416b4cff77285c1f472fc2c4058d8a7554f
git.kernel.org/stable/c/573fb68105... WEB
https://git.kernel.org/stable/c/573fb68105fdc6a127ba6069e58a0d2aff3c9f93
git.kernel.org/stable/c/75d15738fd... WEB
https://git.kernel.org/stable/c/75d15738fd33a782606d0dc80cfeff47edf2ddd8
git.kernel.org/stable/c/94c820d99a... WEB
https://git.kernel.org/stable/c/94c820d99a4305d4ded41a97ed37ec7d26c56e7f
git.kernel.org/stable/c/df7d4d011d... WEB
https://git.kernel.org/stable/c/df7d4d011d5ace20699ea948712f09f9ac08924f

Frequently Asked Questions

What is CVE-2026-89557?
CVE-2026-89557 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-89557?
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-89557?
CVE-2026-89557 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-89557?
CVE-2026-89557 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89557?
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-233m-c5r9-wq53",
  "modified" : "2026-09-14T15:32:29Z",
  "published" : "2026-09-11T21:31:32Z",
  "aliases" : [ "CVE-2026-89557" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmd: do overflow check for sb->bblog_shift in super_1_load()\n\nIn super_1_load(), sb->bblog_shift is an __u8 type value loaded from on-\ndisk superblock. It is used for badblocks API badblocks_set() by the\nfollowing sequence,\n\n 1930   rdev->badblocks.shift = sb->bblog_shift;\n 1931   for (i = 0 ; i < (sectors << (9-3)) ; i++, bbp++) {\n 1932           u64 bb = le64_to_cpu(*bbp);\n 1933           int count = bb & (0x3ff);\n 1934           u64 sector = bb >> 10;\n 1935           sector <<= sb->bblog_shift;\n 1936           count <<= sb->bblog_shift;\n 1937           if (bb + 1 == 0)\n 1938                   break;\n 1939           if (!badblocks_set(&rdev->badblocks, sector, count, 1))\n 1940                   return -EINVAL;\n 1941   }\n\nbb->bblog_shit is in range of 0-255, variable sector is 64bit width, for\nan invalid bb->bblog_shit, it is possible to make sector be overflowed\nby the following calculation,\n 1935           sector <<= sb->bblog_shift;\nThen in turn when call badblocks_set() at line 1939 with the invalid\nrdev->badblocks.shift set at line 1930, may result an overflow inside\n_badblocks_clear() in block/badblocks.c.\n\nAlthough there are many places to call badblocks APIs, the non-zero\nshift value is only used in super_1_load(), other places always use 0 as\nthe shift value. Therefore it is unnecessary to do a general shift value\noverflow check inside badblock API, and just check here as the caller.\n\nThis may avoid unnecessary check, make the badblocks API code more simple\nand elegant.",
  "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-89557"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0a03f9541c06fda64301dcf94f376f07ce2cc396"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/323f3a056dbccb39a642ebde642044a680f3a6d6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/35d522bd32462afcf1981dab6da8a9256c26c1e0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3b097416b4cff77285c1f472fc2c4058d8a7554f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/573fb68105fdc6a127ba6069e58a0d2aff3c9f93"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/75d15738fd33a782606d0dc80cfeff47edf2ddd8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/94c820d99a4305d4ded41a97ed37ec7d26c56e7f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/df7d4d011d5ace20699ea948712f09f9ac08924f"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:39Z"
  }
}