CVE-2026-89560: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-r9r3-96fh-8fhv
Share
CVSS 8.4
Published
Advisory Summary

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

CVE-2026-89560 at a Glance

CVE Identifier CVE-2026-89560
GHSA Identifier GHSA-r9r3-96fh-8fhv
Severity HIGH
CVSS v3.1 Base Score 8.4
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.4

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:C/C:N/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 Changed (S:C)
Confidentiality None (C:N)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-89560

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-89560, 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: landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation Whiteout objects are used in the upper layer of an OverlayFS to indicate that the file with this name does not exist in the unified view, even if it is present in one of the lower layer file systems. For the userspace implementations of OverlayFS (fuse-overlayfs), whiteout objects can be created from userspace as well: * mknod(2) with S_IFCHR and makedev(0, 0) * renameat2(2) with RENAME_WHITEOUT, creating the whiteout in the old place of the moved file. This commit guards whiteout creation in both of these cases with LANDLOCK_ACCESS_FS_MAKE_REG. Whiteout objects are *not* considered character devices and are not bound to a driver. LANDLOCK_ACCESS_FS_MAKE_REG describes the same permission class as a whiteout object: creating one is the only S_IFCHR creation that the VFS exempts from CAP_MKNOD, so it is as unprivileged as creating a regular file, while LANDLOCK_ACCESS_FS_MAKE_CHAR and LANDLOCK_ACCESS_FS_MAKE_BLOCK keep meaning the creation of devices that expose a kernel interface [1]. For the mknod(2) case, introduce a Landlock erratum. The creation of whiteout objects through mknod(2) was previously guarded using LANDLOCK_ACCESS_FS_MAKE_CHAR, and it is now guarded using LANDLOCK_ACCESS_FS_MAKE_REG. For the renameat2(2) case, fix a bug: Before this commit, renameat2(2) with RENAME_WHITEOUT would create a directory entry even when all LANDLOCK_ACCESS_FS_MAKE_* rights were denied. This does not affect normal renames within layered OverlayFS mounts: When doing a regular rename() on a mounted fuse-overlayfs, it is the fuse-overlayfs daemon that exercises renameat2() with RENAME_WHITEOUT, and only the Landlock domain of that daemon is checked there. Depends-on: 49c9e09d9610 ("landlock: Fix handling of disconnected directories") Depends-on: fe72ce6710cb ("landlock: Add errata documentation section") [mic: Record why LANDLOCK_ACCESS_FS_MAKE_REG is the matching right, and add link(2) to the user doc]

References

NVD — CVE-2026-89560 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89560
git.kernel.org/stable/c/0c3204aacb... WEB
https://git.kernel.org/stable/c/0c3204aacbe8c07f9e87e3028f28ec6c166a1075
git.kernel.org/stable/c/39fc165977... WEB
https://git.kernel.org/stable/c/39fc16597715125529df8f94e016fb00836ee3c1
git.kernel.org/stable/c/627ce4902d... WEB
https://git.kernel.org/stable/c/627ce4902df1d737e99306daae5a87c68b876d16
git.kernel.org/stable/c/672fa082d4... WEB
https://git.kernel.org/stable/c/672fa082d48b21e1fb62cdb184fee41513e53421
git.kernel.org/stable/c/d739e32318... WEB
https://git.kernel.org/stable/c/d739e32318479086efb8a6bcf5d37cf341b51f8f
git.kernel.org/stable/c/dfb10d9890... WEB
https://git.kernel.org/stable/c/dfb10d989056181168ebc16781a8f39520e33200
git.kernel.org/stable/c/efb4f24fc2... WEB
https://git.kernel.org/stable/c/efb4f24fc2b9bcef1c41ff3392894f1fa8fba2a0

Frequently Asked Questions

What is CVE-2026-89560?
CVE-2026-89560 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-89560?
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-89560?
CVE-2026-89560 has a CVSS v3.1 base score of 8.4 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H.
What CWE is associated with CVE-2026-89560?
CVE-2026-89560 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89560?
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-r9r3-96fh-8fhv",
  "modified" : "2026-10-03T12:31:06Z",
  "published" : "2026-09-11T21:31:32Z",
  "aliases" : [ "CVE-2026-89560" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nlandlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation\n\nWhiteout objects are used in the upper layer of an OverlayFS to\nindicate that the file with this name does not exist in the unified\nview, even if it is present in one of the lower layer file systems.\n\nFor the userspace implementations of OverlayFS (fuse-overlayfs),\nwhiteout objects can be created from userspace as well:\n\n* mknod(2) with S_IFCHR and makedev(0, 0)\n* renameat2(2) with RENAME_WHITEOUT,\n  creating the whiteout in the old place of the moved file.\n\nThis commit guards whiteout creation in both of these cases with\nLANDLOCK_ACCESS_FS_MAKE_REG.  Whiteout objects are *not* considered\ncharacter devices and are not bound to a driver.\n\nLANDLOCK_ACCESS_FS_MAKE_REG describes the same permission class as a\nwhiteout object: creating one is the only S_IFCHR creation that the VFS\nexempts from CAP_MKNOD, so it is as unprivileged as creating a regular\nfile, while LANDLOCK_ACCESS_FS_MAKE_CHAR and\nLANDLOCK_ACCESS_FS_MAKE_BLOCK keep meaning the creation of devices that\nexpose a kernel interface [1].\n\nFor the mknod(2) case, introduce a Landlock erratum.  The creation of\nwhiteout objects through mknod(2) was previously guarded using\nLANDLOCK_ACCESS_FS_MAKE_CHAR, and it is now guarded using\nLANDLOCK_ACCESS_FS_MAKE_REG.\n\nFor the renameat2(2) case, fix a bug: Before this commit, renameat2(2)\nwith RENAME_WHITEOUT would create a directory entry even when all\nLANDLOCK_ACCESS_FS_MAKE_* rights were denied.\n\nThis does not affect normal renames within layered OverlayFS mounts:\nWhen doing a regular rename() on a mounted fuse-overlayfs, it is the\nfuse-overlayfs daemon that exercises renameat2() with RENAME_WHITEOUT,\nand only the Landlock domain of that daemon is checked there.\n\nDepends-on: 49c9e09d9610 (\"landlock: Fix handling of disconnected directories\")\nDepends-on: fe72ce6710cb (\"landlock: Add errata documentation section\")\n[mic: Record why LANDLOCK_ACCESS_FS_MAKE_REG is the matching right, and\nadd link(2) to the user doc]",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89560"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0c3204aacbe8c07f9e87e3028f28ec6c166a1075"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/39fc16597715125529df8f94e016fb00836ee3c1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/627ce4902df1d737e99306daae5a87c68b876d16"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/672fa082d48b21e1fb62cdb184fee41513e53421"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d739e32318479086efb8a6bcf5d37cf341b51f8f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dfb10d989056181168ebc16781a8f39520e33200"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/efb4f24fc2b9bcef1c41ff3392894f1fa8fba2a0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:39Z"
  }
}