CVE-2026-89930: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-j569-2qg3-pw8x
Share
CVSS 9.3
Published
Advisory Summary

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

CVE Identifier CVE-2026-89930
GHSA Identifier GHSA-j569-2qg3-pw8x
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-89930

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-89930, 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: nVMX: Service local TLB flushes on failed nested VM-Enter KVM services local TLB flushes on "full" nested VM-Exits (through __nested_vmx_vmexit()), but not if a nested VM-Enter fails (e.g. due to failed VMCS checks in nested_vmx_enter_non_root_mode()). However, it is possible that KVM had queued TLB flushes that need to be performed, even if the nested VM-Enter was not successful. For example, if VPID is disabled for L2 (via nested_vmx_transition_tlb_flush(), or if via the MSR load lists, as the SDM says: If any MSR is being loaded in such a way that would architecturally require a TLB flush, the TLBs are updated so that, after VM entry, the logical processor will not use any translations that were cached before the transition. The SDM is unclear about when the TLB flush should occur, and whether or not a failed VM entry would flush the TLB, so it is safer to always do the TLB flush in this case. More concretely, KVM also updates the last VPID L1 used for L2 in nested_vmx_transition_tlb_flush() (i.e. last_vpid), even if the VM entry ultimately fails. With the current code, KVM could miss a TLB flush if L1 changes L2's VPID, then does a failed VM entry followed by a successful one, as the failed VM entry would update last_vpid but not actually flush the TLB. Servicing local TLB flushes on failed VM entries makes sure that the TLB is always flushed when last_vpid is updated.

References

NVD — CVE-2026-89930 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89930
git.kernel.org/stable/c/05a0b701d1... WEB
https://git.kernel.org/stable/c/05a0b701d1089fb57beeb8982f23c3bbafe0fa8b
git.kernel.org/stable/c/1025b938dc... WEB
https://git.kernel.org/stable/c/1025b938dc439b75c720a568a855a13eeb245686
git.kernel.org/stable/c/312cdb6d89... WEB
https://git.kernel.org/stable/c/312cdb6d8940827dea63a7a52fb714a5049f06d1
git.kernel.org/stable/c/62c3ee4c9f... WEB
https://git.kernel.org/stable/c/62c3ee4c9f0e2efef5157358b3549e50ede96d73
git.kernel.org/stable/c/c0c66cd575... WEB
https://git.kernel.org/stable/c/c0c66cd575e31218da6a7d104c6ef80b0830b60c
git.kernel.org/stable/c/c43563e751... WEB
https://git.kernel.org/stable/c/c43563e7518e65ec6ccaa6a65f84c5af5ca5d379
git.kernel.org/stable/c/f74fccdf4f... WEB
https://git.kernel.org/stable/c/f74fccdf4f7fb0780cd84944108d35f3d9dc46a7

Frequently Asked Questions

What is CVE-2026-89930?
CVE-2026-89930 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-89930?
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-89930?
CVE-2026-89930 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-89930?
CVE-2026-89930 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89930?
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-j569-2qg3-pw8x",
  "modified" : "2026-09-16T15:31:02Z",
  "published" : "2026-09-16T12:30:41Z",
  "aliases" : [ "CVE-2026-89930" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: nVMX: Service local TLB flushes on failed nested VM-Enter\n\nKVM services local TLB flushes on \"full\" nested VM-Exits (through\n__nested_vmx_vmexit()), but not if a nested VM-Enter fails (e.g. due to\nfailed VMCS checks in nested_vmx_enter_non_root_mode()).\n\nHowever, it is possible that KVM had queued TLB flushes that need to be\nperformed, even if the nested VM-Enter was not successful. For example,\nif VPID is disabled for L2 (via nested_vmx_transition_tlb_flush(), or if\nvia the MSR load lists, as the SDM says:\n\n  If any MSR is being loaded in such a way that would architecturally\n  require a TLB flush, the TLBs are updated so that, after VM entry, the\n  logical processor will not use any translations that were cached before\n  the transition.\n\nThe SDM is unclear about when the TLB flush should occur, and whether or\nnot a failed VM entry would flush the TLB, so it is safer to always\ndo the TLB flush in this case.\n\nMore concretely, KVM also updates the last VPID L1 used for L2 in\nnested_vmx_transition_tlb_flush() (i.e. last_vpid), even if the VM entry\nultimately fails. With the current code, KVM could miss a TLB flush if\nL1 changes L2's VPID, then does a failed VM entry followed by a\nsuccessful one, as the failed VM entry would update last_vpid but not\nactually flush the TLB. Servicing local TLB flushes on failed VM entries\nmakes sure that the TLB is always flushed when last_vpid is updated.",
  "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-89930"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/05a0b701d1089fb57beeb8982f23c3bbafe0fa8b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1025b938dc439b75c720a568a855a13eeb245686"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/312cdb6d8940827dea63a7a52fb714a5049f06d1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/62c3ee4c9f0e2efef5157358b3549e50ede96d73"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c0c66cd575e31218da6a7d104c6ef80b0830b60c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c43563e7518e65ec6ccaa6a65f84c5af5ca5d379"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f74fccdf4f7fb0780cd84944108d35f3d9dc46a7"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:02Z"
  }
}