CVE-2026-68293: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-7555-mcj4-25r2
Share
CVSS 7.1
CWE-122
Published
Advisory Summary

CVE-2026-68293 is a HIGH (CVSS 7.1) security vulnerability vulnerability (CWE-122: Heap-based Buffer Overflow) affecting Software libraries in the Maven ecosystem. The weakness occurs when a heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68293 at a Glance

CVE Identifier CVE-2026-68293
GHSA Identifier GHSA-7555-mcj4-25r2
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification CWE-122: Heap-based Buffer Overflow
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.1

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:U/C:H/I:N/A:H).

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

How to Fix CVE-2026-68293

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-68293, 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-122: Heap-based Buffer Overflow, where a heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). 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: net/mlx5: Fix MCIA register buffer overflow on 32 dword reads The MCIA register can return up to 32 dwords (128 bytes) when the device advertises the mcia_32dwords capability, but struct mlx5_ifc_mcia_reg_bits only defines dword_0..11, leaving room for just 12 dwords (48 bytes) of data. mlx5_query_mcia() clamps the read size to mlx5_mcia_max_bytes() and then memcpy()s that many bytes out of the register, potentially reading past the end of the 'out' buffer. On kernels built with FORTIFY_SOURCE this is caught as a buffer overflow while reading the module EEPROM via ethtool: detected buffer overflow in memcpy kernel BUG at lib/string_helpers.c:1048! RIP: 0010:fortify_panic+0x13/0x20 Call Trace: mlx5_query_mcia.isra.0+0x200/0x210 [mlx5_core] mlx5_query_module_eeprom_by_page+0x4a/0xa0 [mlx5_core] mlx5e_get_module_eeprom_by_page+0xbb/0x120 [mlx5_core] eeprom_prepare_data+0xf3/0x170 ethnl_default_doit+0xf1/0x3b0 Extend the mcia_reg layout to 32 dwords.

References

NVD — CVE-2026-68293 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68293
git.kernel.org/stable/c/11c057d234... WEB
https://git.kernel.org/stable/c/11c057d23465c7a5817a7284c896d19d54c0b616
git.kernel.org/stable/c/5be4eebd5a... WEB
https://git.kernel.org/stable/c/5be4eebd5a3a198dab0adcd550e1cadca79bdfed
git.kernel.org/stable/c/87b39a8c87... WEB
https://git.kernel.org/stable/c/87b39a8c875ca744b7de69af0a8ef8874cffccf1
git.kernel.org/stable/c/88b2a16dda... WEB
https://git.kernel.org/stable/c/88b2a16ddac3357e3f1d528e758b51e2c945d546

Frequently Asked Questions

What is CVE-2026-68293?
CVE-2026-68293 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-122: Heap-based Buffer Overflow.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68293?
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-68293?
CVE-2026-68293 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H.
What CWE is associated with CVE-2026-68293?
CVE-2026-68293 is classified under CWE-122: Heap-based Buffer Overflow (A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().).
How can I check Maven dependencies for CVE-2026-68293?
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-7555-mcj4-25r2",
  "modified" : "2026-08-14T00:31:54Z",
  "published" : "2026-08-10T15:33:45Z",
  "aliases" : [ "CVE-2026-68293" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Fix MCIA register buffer overflow on 32 dword reads\n\nThe MCIA register can return up to 32 dwords (128 bytes) when the device\nadvertises the mcia_32dwords capability, but struct\nmlx5_ifc_mcia_reg_bits only defines dword_0..11, leaving room for just\n12 dwords (48 bytes) of data.\n\nmlx5_query_mcia() clamps the read size to mlx5_mcia_max_bytes() and then\nmemcpy()s that many bytes out of the register, potentially reading past\nthe end of the 'out' buffer. On kernels built with FORTIFY_SOURCE this\nis caught as a buffer overflow while reading the module EEPROM via\nethtool:\n\n  detected buffer overflow in memcpy\n  kernel BUG at lib/string_helpers.c:1048!\n  RIP: 0010:fortify_panic+0x13/0x20\n  Call Trace:\n   mlx5_query_mcia.isra.0+0x200/0x210 [mlx5_core]\n   mlx5_query_module_eeprom_by_page+0x4a/0xa0 [mlx5_core]\n   mlx5e_get_module_eeprom_by_page+0xbb/0x120 [mlx5_core]\n   eeprom_prepare_data+0xf3/0x170\n   ethnl_default_doit+0xf1/0x3b0\n\nExtend the mcia_reg layout to 32 dwords.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68293"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/11c057d23465c7a5817a7284c896d19d54c0b616"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5be4eebd5a3a198dab0adcd550e1cadca79bdfed"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/87b39a8c875ca744b7de69af0a8ef8874cffccf1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/88b2a16ddac3357e3f1d528e758b51e2c945d546"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-122" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:20:18Z"
  }
}