CVE-2026-89770: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-p8q7-qqp3-r9v3
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-89770
GHSA Identifier GHSA-p8q7-qqp3-r9v3
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-89770

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-89770, 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: iomap: don't free integrity payload that doesn't exist fs_bio_integrity_alloc might not allocate a bio integrity payload if PI verification is disabled on the block device. Check for that case before calling fs_bio_integrity_free in iomap_bio_read_folio_range_sync to avoid a NULL pointer dereferences. Make the branch cover the PI verification as well - while fs_bio_integrity_verify works without an integrity payload, it requires one to actually do useful work.

References

NVD — CVE-2026-89770 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89770
git.kernel.org/stable/c/65651f1001... WEB
https://git.kernel.org/stable/c/65651f1001aa3638909bc58c7b2b46160692757b
git.kernel.org/stable/c/8a8685b32c... WEB
https://git.kernel.org/stable/c/8a8685b32c0718cc7b2cb4d6202e5a5b8e0a8e2d

Frequently Asked Questions

What is CVE-2026-89770?
CVE-2026-89770 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-89770?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89770?
CVE-2026-89770 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89770?
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-p8q7-qqp3-r9v3",
  "modified" : "2026-09-11T21:31:39Z",
  "published" : "2026-09-11T21:31:39Z",
  "aliases" : [ "CVE-2026-89770" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\niomap: don't free integrity payload that doesn't exist\n\nfs_bio_integrity_alloc might not allocate a bio integrity payload if PI\nverification is disabled on the block device.  Check for that case before\ncalling fs_bio_integrity_free in iomap_bio_read_folio_range_sync to\navoid a NULL pointer dereferences.\n\nMake the branch cover the PI verification as well - while\nfs_bio_integrity_verify works without an integrity payload, it requires\none to actually do useful work.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89770"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/65651f1001aa3638909bc58c7b2b46160692757b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8a8685b32c0718cc7b2cb4d6202e5a5b8e0a8e2d"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:20:08Z"
  }
}