CVE-2026-89766: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-7f3v-362v-5m4g
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-89766
GHSA Identifier GHSA-7f3v-362v-5m4g
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-89766

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-89766, 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: pidfd: hold exec_update_lock around namespace ioctl The PIDFD_GET_*_NAMESPACE ioctls in pidfd_ioctl() perform a filesystem credentials ptrace access check before handing out a namespace file descriptor. The accompanying comment states that the code "mirrors nsfs behavior", but, unlike the corresponding procfs paths, it does so without holding the target task's exec_update_lock. proc_ns_get_link() and proc_ns_readlink() both take exec_update_lock for reading around the ptrace check and the namespace lookup, so that the credentials used for the access decision match those of the task when its namespace is read. Without it, a caller can pass the check against the target's old credentials and then read the namespace after the target has execve()'d a setuid binary and committed new credentials -- accessing namespace information it should have been denied. Hold exec_update_lock for reading around the ptrace check and the namespace lookup so that pidfd truly mirrors nsfs behavior, as the comment already claims. open_namespace() itself runs outside the lock: once a namespace reference is obtained it carries its own refcount and is opened with the caller's own credentials, so a concurrent execve() on the target can no longer affect the outcome.

References

NVD — CVE-2026-89766 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89766
git.kernel.org/stable/c/9688a46802... WEB
https://git.kernel.org/stable/c/9688a46802939da28f00cb40e8129615d5d4af39
git.kernel.org/stable/c/bac2f1913a... WEB
https://git.kernel.org/stable/c/bac2f1913a216677c2c220d7bb352dd0330065ca
git.kernel.org/stable/c/cf24ce48d6... WEB
https://git.kernel.org/stable/c/cf24ce48d60225fdbee68ed2058763a1fd172ff3
git.kernel.org/stable/c/e89318aa86... WEB
https://git.kernel.org/stable/c/e89318aa8629969e86548b05e7c19283af3f0efb

Frequently Asked Questions

What is CVE-2026-89766?
CVE-2026-89766 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-89766?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89766?
CVE-2026-89766 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89766?
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-7f3v-362v-5m4g",
  "modified" : "2026-10-03T12:31:06Z",
  "published" : "2026-09-11T21:31:39Z",
  "aliases" : [ "CVE-2026-89766" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\npidfd: hold exec_update_lock around namespace ioctl\n\nThe PIDFD_GET_*_NAMESPACE ioctls in pidfd_ioctl() perform a filesystem\ncredentials ptrace access check before handing out a namespace file\ndescriptor.  The accompanying comment states that the code \"mirrors nsfs\nbehavior\", but, unlike the corresponding procfs paths, it does so without\nholding the target task's exec_update_lock.\n\nproc_ns_get_link() and proc_ns_readlink() both take exec_update_lock for\nreading around the ptrace check and the namespace lookup, so that the\ncredentials used for the access decision match those of the task when its\nnamespace is read.  Without it, a caller can pass the check against the\ntarget's old credentials and then read the namespace after the target has\nexecve()'d a setuid binary and committed new credentials -- accessing\nnamespace information it should have been denied.\n\nHold exec_update_lock for reading around the ptrace check and the\nnamespace lookup so that pidfd truly mirrors nsfs behavior, as the comment\nalready claims.  open_namespace() itself runs outside the lock: once a\nnamespace reference is obtained it carries its own refcount and is opened\nwith the caller's own credentials, so a concurrent execve() on the target\ncan no longer affect the outcome.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89766"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9688a46802939da28f00cb40e8129615d5d4af39"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bac2f1913a216677c2c220d7bb352dd0330065ca"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cf24ce48d60225fdbee68ed2058763a1fd172ff3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e89318aa8629969e86548b05e7c19283af3f0efb"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:20:07Z"
  }
}