CVE-2026-80699: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-4f2r-mgjf-292r
Published
Advisory Summary

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

CVE Identifier CVE-2026-80699
GHSA Identifier GHSA-4f2r-mgjf-292r
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-80699

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-80699, 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: vgic: Avoid double-deactivate of IRQs in the nested context In the nested state, the physical interrupt has already been deactivated through the HW bit in the LR. The extra deactivation would be harmless but can hit an errata case on AmpereOne, so avoid it here. On AmpereOne, deactivating a physical interrupt through ICC_DIR_EL1 or ICC_EOIR1_EL1 (depending on EOImode) which is not active, but is the highest priority pending interrupt causes the cpu to lose the interrupt pending state and also prevents the delivery of future interrupts.

References

Frequently Asked Questions

What is CVE-2026-80699?
CVE-2026-80699 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-80699?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-80699?
CVE-2026-80699 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-80699?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4f2r-mgjf-292r",
  "modified" : "2026-08-28T09:31:49Z",
  "published" : "2026-08-28T09:31:49Z",
  "aliases" : [ "CVE-2026-80699" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: vgic: Avoid double-deactivate of IRQs in the nested context\n\nIn the nested state, the physical interrupt has already been\ndeactivated through the HW bit in the LR. The extra deactivation\nwould be harmless but can hit an errata case on AmpereOne, so\navoid it here.\n\nOn AmpereOne, deactivating a physical interrupt through\nICC_DIR_EL1 or ICC_EOIR1_EL1 (depending on EOImode) which is not\nactive, but is the highest priority pending interrupt causes the\ncpu to lose the interrupt pending state and also prevents the\ndelivery of future interrupts.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80699"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8a570b19b4b16a8a3b5ffa2b332bd5613110b2d8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f78f08b38a7f121c7d6b3e41002d9de7fd3c9189"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-28T08:16:55Z"
  }
}