CVE-2026-68129: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-wqfg-pmq9-xr26
Share
CVSS 7.5
CWE-400
Published
Advisory Summary

CVE-2026-68129 is a HIGH (CVSS 7.5) security vulnerability vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not properly control the allocation and maintenance of a limited resource.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68129 at a Glance

CVE Identifier CVE-2026-68129
GHSA Identifier GHSA-wqfg-pmq9-xr26
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

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

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

How to Fix CVE-2026-68129

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-68129, 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-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. 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: gve: fix Rx queue stall on alloc failure When the system is under extreme memory pressure, page allocations can fail during the Rx buffer refill loop. If the number of buffers posted to hardware falls below a critical low threshold and the refill loop exits due to allocation failures, the queue can stall: 1. The device drops incoming packets because there are no descriptors. 2. Since no packets are processed, no Rx completions are generated. 3. Because no completions occur, NAPI is never scheduled, preventing the refill loop from running again even after memory is freed. This results in a permanent queue stall. Resolve this by introducing a starvation recovery timer for each Rx queue. If the number of buffers posted to hardware falls below a critical low threshold, start a timer to periodically reschedule NAPI. Once NAPI runs and successfully refills the queue above the threshold, the timer is not rescheduled. The threshold is set to 32 because a single maximum-sized Receive Segment Coalescing (RSC) packet can consume up to 19 descriptors in the Rx path. Lower thresholds (such as 8 or 16) would be insufficient to process a complete maximum-sized RSC packet, risking packet drops or unexpected hardware behavior under memory pressure. Setting the threshold to 32 guarantees a safe margin to handle at least one full RSC packet.

References

NVD — CVE-2026-68129 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68129
git.kernel.org/stable/c/0c317349b4... WEB
https://git.kernel.org/stable/c/0c317349b4baa5038d1fc373bf46d5a2419d1710
git.kernel.org/stable/c/299d5728a7... WEB
https://git.kernel.org/stable/c/299d5728a7312fdd02059b074aebbe4ebbd391e4
git.kernel.org/stable/c/42d525e751... WEB
https://git.kernel.org/stable/c/42d525e751c61b876b2b0ae4e71ba7a8ab0c2777
git.kernel.org/stable/c/689b9f588d... WEB
https://git.kernel.org/stable/c/689b9f588d2d7323dc66293fe594a68d030f400f
git.kernel.org/stable/c/91e0249f3e... WEB
https://git.kernel.org/stable/c/91e0249f3ef62b75fe8c9c9372eaba32876e4b3a
git.kernel.org/stable/c/9db46e19e5... WEB
https://git.kernel.org/stable/c/9db46e19e5d6bdcd4bf811284a5b0df1b984ef80
git.kernel.org/stable/c/b65352a1ba... WEB
https://git.kernel.org/stable/c/b65352a1bac64442ad95e64f385b40ccb9f1b0db

Frequently Asked Questions

What is CVE-2026-68129?
CVE-2026-68129 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-400: Uncontrolled Resource Consumption.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68129?
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-68129?
CVE-2026-68129 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-68129?
CVE-2026-68129 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check Maven dependencies for CVE-2026-68129?
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-wqfg-pmq9-xr26",
  "modified" : "2026-08-19T18:32:06Z",
  "published" : "2026-08-10T15:33:37Z",
  "aliases" : [ "CVE-2026-68129" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ngve: fix Rx queue stall on alloc failure\n\nWhen the system is under extreme memory pressure, page allocations can\nfail during the Rx buffer refill loop. If the number of buffers posted\nto hardware falls below a critical low threshold and the refill loop\nexits due to allocation failures, the queue can stall:\n\n1. The device drops incoming packets because there are no descriptors.\n2. Since no packets are processed, no Rx completions are generated.\n3. Because no completions occur, NAPI is never scheduled, preventing\n   the refill loop from running again even after memory is freed.\n\nThis results in a permanent queue stall.\n\nResolve this by introducing a starvation recovery timer for each Rx queue.\nIf the number of buffers posted to hardware falls below a critical low\nthreshold, start a timer to periodically reschedule NAPI. Once NAPI runs\nand successfully refills the queue above the threshold, the timer is\nnot rescheduled.\n\nThe threshold is set to 32 because a single maximum-sized Receive Segment\nCoalescing (RSC) packet can consume up to 19 descriptors in the Rx path.\nLower thresholds (such as 8 or 16) would be insufficient to process a\ncomplete maximum-sized RSC packet, risking packet drops or unexpected\nhardware behavior under memory pressure. Setting the threshold to 32\nguarantees a safe margin to handle at least one full RSC packet.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68129"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0c317349b4baa5038d1fc373bf46d5a2419d1710"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/299d5728a7312fdd02059b074aebbe4ebbd391e4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/42d525e751c61b876b2b0ae4e71ba7a8ab0c2777"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/689b9f588d2d7323dc66293fe594a68d030f400f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/91e0249f3ef62b75fe8c9c9372eaba32876e4b3a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9db46e19e5d6bdcd4bf811284a5b0df1b984ef80"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b65352a1bac64442ad95e64f385b40ccb9f1b0db"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:19:58Z"
  }
}