CVE-2026-89916: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-5p99-rg43-px7f
Share
CVSS 9.3
Published
Advisory Summary

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

CVE-2026-89916 at a Glance

CVE Identifier CVE-2026-89916
GHSA Identifier GHSA-5p99-rg43-px7f
Severity CRITICAL
CVSS v3.1 Base Score 9.3
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-89916

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-89916, 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: KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry A VNCR TLB invalidation can occur on one vcpu while another vcpu is faulting in this same page. Without correctly handling this, we can end up with the following scenario: - vcpu A walks the PTs to translate VNCR - before vcpu A is able to grab the MMU lock to insert the TLB, vcpu B updates the S1 PTs with an invalid entry, and issues a TLBI S1E2 for this VA - vcpu A inserts the TLB for something that is now invalid This isn't a new problem, and we manage S2 by having the MMU notifier to bump up mmu_invalidate_seq on invalidation so that the fault can be replayed. We can perform something similar here, and extend invalidate_vncr_va() to update the same counter, clearly indicating that the context has changed under our feet. This is safe as the invalidation always happen while holding the MMU lock for write, and that we sample the sequence number before walking S1.

References

NVD — CVE-2026-89916 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89916
git.kernel.org/stable/c/11ee3faab4... WEB
https://git.kernel.org/stable/c/11ee3faab4f1755d126bead9f882e75a7a677860
git.kernel.org/stable/c/2b7324f3a0... WEB
https://git.kernel.org/stable/c/2b7324f3a0c1072b9d578b8d42f199506753f26e
git.kernel.org/stable/c/d8580e7aa1... WEB
https://git.kernel.org/stable/c/d8580e7aa189b0c6c5bb4d94b8352728a7c35bbd

Frequently Asked Questions

What is CVE-2026-89916?
CVE-2026-89916 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-89916?
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-89916?
CVE-2026-89916 has a CVSS v3.1 base score of 9.3 (CRITICAL) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-89916?
CVE-2026-89916 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89916?
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-5p99-rg43-px7f",
  "modified" : "2026-09-16T15:31:02Z",
  "published" : "2026-09-16T12:30:41Z",
  "aliases" : [ "CVE-2026-89916" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Make VNCR invalidation participate in MMU invalidation retry\n\nA VNCR TLB invalidation can occur on one vcpu while another vcpu is\nfaulting in this same page. Without correctly handling this, we can\nend up with the following scenario:\n\n- vcpu A walks the PTs to translate VNCR\n- before vcpu A is able to grab the MMU lock to insert the TLB,\n  vcpu B updates the S1 PTs with an invalid entry, and issues\n  a TLBI S1E2 for this VA\n- vcpu A inserts the TLB for something that is now invalid\n\nThis isn't a new problem, and we manage S2 by having the MMU notifier\nto bump up mmu_invalidate_seq on invalidation so that the fault can be\nreplayed.\n\nWe can perform something similar here, and extend invalidate_vncr_va() to\nupdate the same counter, clearly indicating that the context has\nchanged under our feet. This is safe as the invalidation always happen\nwhile holding the MMU lock for write, and that we sample the sequence\nnumber before walking S1.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89916"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/11ee3faab4f1755d126bead9f882e75a7a677860"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2b7324f3a0c1072b9d578b8d42f199506753f26e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d8580e7aa189b0c6c5bb4d94b8352728a7c35bbd"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:00Z"
  }
}