CVE-2026-89595: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-h76q-h94r-6qmf
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-89595
GHSA Identifier GHSA-h76q-h94r-6qmf
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-89595

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-89595, 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: fsnotify: Fix stale object mask after concurrent mark updates When a mark gets a new event bit, fanotify and inotify may avoid recalculating the object mask if the cached aggregate already contains that bit. This is racy with a recalculation triggered by a concurrent update to another mark on the same connector. The concurrent scan can read the mark before the new bit is added, while the updater reads the old aggregate before that scan publishes its result. The updater then skips recalculation and the scan publishes a mask without the bit, leaving the object mask stale after both updates complete. This can be reproduced with two fanotify groups watching the same inode: one thread removes FAN_MODIFY from one existing mark while another thread adds FAN_MODIFY to the other mark. After both fanotify_mark() calls return, writes can fail to produce FAN_MODIFY for the group whose mark now contains the bit. This was reproduced on an unmodified v6.12.95 kernel. The equivalent inotify interleaving loses IN_MODIFY events. For normal fanotify additions, recalculate whenever the raw mark mask changes. The normal mask is not cleared asynchronously, so an unchanged addition cannot introduce missing interest. Always recalculate ignore-mask updates because FS_MODIFY handling may clear the ignore mask without taking mark->lock, making snapshot comparisons unreliable. Always recalculate after updating an existing inotify watch. Its replace path temporarily sets mark->mask to zero, so a concurrent scan can observe zero even when the old and final masks are equal. Assigning the replacement mask directly would avoid the transient zero, but existing-watch updates are infrequent, so unconditional recalculation is simpler.

References

NVD — CVE-2026-89595 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89595
git.kernel.org/stable/c/27d172b60e... WEB
https://git.kernel.org/stable/c/27d172b60eeca5c8fd51b246f9fb959067cf102b
git.kernel.org/stable/c/2f09f08d60... WEB
https://git.kernel.org/stable/c/2f09f08d602647fc4e328fc27ecb4c3008d10338
git.kernel.org/stable/c/343ae18e96... WEB
https://git.kernel.org/stable/c/343ae18e960f6c5f1d34d58a69750c62cd463228
git.kernel.org/stable/c/92289e6663... WEB
https://git.kernel.org/stable/c/92289e66639f62abc754c6f3bce5ead7e98e4ee2
git.kernel.org/stable/c/947400af98... WEB
https://git.kernel.org/stable/c/947400af98b9e63841929d079a2c3ea0a8ba227b
git.kernel.org/stable/c/ac8d8b599d... WEB
https://git.kernel.org/stable/c/ac8d8b599d466a129122bded77db3d0f8b96b461
git.kernel.org/stable/c/de75382d6e... WEB
https://git.kernel.org/stable/c/de75382d6e354b2b055df4896d12a91969f12090
git.kernel.org/stable/c/e422777fdd... WEB
https://git.kernel.org/stable/c/e422777fdd4746de1109575c51e65038d4c5c1be

Frequently Asked Questions

What is CVE-2026-89595?
CVE-2026-89595 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-89595?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89595?
CVE-2026-89595 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89595?
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-h76q-h94r-6qmf",
  "modified" : "2026-09-14T15:32:30Z",
  "published" : "2026-09-11T21:31:33Z",
  "aliases" : [ "CVE-2026-89595" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfsnotify: Fix stale object mask after concurrent mark updates\n\nWhen a mark gets a new event bit, fanotify and inotify may avoid\nrecalculating the object mask if the cached aggregate already contains that\nbit. This is racy with a recalculation triggered by a concurrent update to\nanother mark on the same connector.\n\nThe concurrent scan can read the mark before the new bit is added, while\nthe updater reads the old aggregate before that scan publishes its result.\nThe updater then skips recalculation and the scan publishes a mask without\nthe bit, leaving the object mask stale after both updates complete.\n\nThis can be reproduced with two fanotify groups watching the same inode:\none thread removes FAN_MODIFY from one existing mark while another thread\nadds FAN_MODIFY to the other mark. After both fanotify_mark() calls return,\nwrites can fail to produce FAN_MODIFY for the group whose mark now contains\nthe bit. This was reproduced on an unmodified v6.12.95 kernel. The\nequivalent inotify interleaving loses IN_MODIFY events.\n\nFor normal fanotify additions, recalculate whenever the raw mark mask\nchanges. The normal mask is not cleared asynchronously, so an unchanged\naddition cannot introduce missing interest. Always recalculate ignore-mask\nupdates because FS_MODIFY handling may clear the ignore mask without taking\nmark->lock, making snapshot comparisons unreliable.\n\nAlways recalculate after updating an existing inotify watch. Its replace\npath temporarily sets mark->mask to zero, so a concurrent scan can observe\nzero even when the old and final masks are equal. Assigning the replacement\nmask directly would avoid the transient zero, but existing-watch updates\nare infrequent, so unconditional recalculation is simpler.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89595"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/27d172b60eeca5c8fd51b246f9fb959067cf102b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2f09f08d602647fc4e328fc27ecb4c3008d10338"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/343ae18e960f6c5f1d34d58a69750c62cd463228"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/92289e66639f62abc754c6f3bce5ead7e98e4ee2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/947400af98b9e63841929d079a2c3ea0a8ba227b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ac8d8b599d466a129122bded77db3d0f8b96b461"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/de75382d6e354b2b055df4896d12a91969f12090"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e422777fdd4746de1109575c51e65038d4c5c1be"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:44Z"
  }
}