CVE-2026-46076: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-gj33-hwgc-v3v8
Share
CVSS 7.9
CWE-863
Published
Advisory Summary

CVE-2026-46076 is a HIGH (CVSS 7.9) security vulnerability vulnerability (CWE-863: Incorrect Authorization) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-46076 at a Glance

CVE Identifier CVE-2026-46076
GHSA Identifier GHSA-gj33-hwgc-v3v8
Severity HIGH
CVSS v3.1 Base Score 7.9
CWE Classification CWE-863: Incorrect Authorization
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.9

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:L/I:L/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 Low (C:L)
Integrity Low (I:L)
Availability High (A:H)

How to Fix CVE-2026-46076

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-46076, 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 CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. 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: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 Explicitly synthesize a #UD for VMMCALL if L2 is active, L1 does NOT want to intercept VMMCALL, nested_svm_l2_tlb_flush_enabled() is true, and the hypercall is something other than one of the supported Hyper-V hypercalls. When all of the above conditions are met, KVM will intercept VMMCALL but never forward it to L1, i.e. will let L2 make hypercalls as if it were L1. The TLFS says a whole lot of nothing about this scenario, so go with the architectural behavior, which says that VMMCALL #UDs if it's not intercepted. Opportunistically do a 2-for-1 stub trade by stub-ifying the new API instead of the helpers it uses. The last remaining "single" stub will soon be dropped as well. [sean: rewrite changelog and comment, tag for stable, remove defunct stubs]

References

NVD — CVE-2026-46076 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-46076
git.kernel.org/stable/c/009c0f726a... WEB
https://git.kernel.org/stable/c/009c0f726abeaa67aad1d96b883bdce01d405ce2
git.kernel.org/stable/c/5fb4a5f361... WEB
https://git.kernel.org/stable/c/5fb4a5f361565f5b629d8a8fe5288ce8463c5727
git.kernel.org/stable/c/924d721fae... WEB
https://git.kernel.org/stable/c/924d721fae95687acedbaf624a094ed0e8b67104
git.kernel.org/stable/c/c36991c6f8... WEB
https://git.kernel.org/stable/c/c36991c6f8d2ab56ee67aff04e3c357f45cfc76c

Frequently Asked Questions

What is CVE-2026-46076?
CVE-2026-46076 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-863: Incorrect Authorization.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-46076?
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-46076?
CVE-2026-46076 has a CVSS v3.1 base score of 7.9 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H.
What CWE is associated with CVE-2026-46076?
CVE-2026-46076 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Maven dependencies for CVE-2026-46076?
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-gj33-hwgc-v3v8",
  "modified" : "2026-05-30T12:30:24Z",
  "published" : "2026-05-27T15:33:23Z",
  "aliases" : [ "CVE-2026-46076" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1\n\nExplicitly synthesize a #UD for VMMCALL if L2 is active, L1 does NOT want\nto intercept VMMCALL, nested_svm_l2_tlb_flush_enabled() is true, and the\nhypercall is something other than one of the supported Hyper-V hypercalls.\nWhen all of the above conditions are met, KVM will intercept VMMCALL but\nnever forward it to L1, i.e. will let L2 make hypercalls as if it were L1.\n\nThe TLFS says a whole lot of nothing about this scenario, so go with the\narchitectural behavior, which says that VMMCALL #UDs if it's not\nintercepted.\n\nOpportunistically do a 2-for-1 stub trade by stub-ifying the new API\ninstead of the helpers it uses.  The last remaining \"single\" stub will\nsoon be dropped as well.\n\n[sean: rewrite changelog and comment, tag for stable, remove defunct stubs]",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46076"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/009c0f726abeaa67aad1d96b883bdce01d405ce2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5fb4a5f361565f5b629d8a8fe5288ce8463c5727"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/924d721fae95687acedbaf624a094ed0e8b67104"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c36991c6f8d2ab56ee67aff04e3c357f45cfc76c"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-27T14:17:28Z"
  }
}