CVE-2026-68388: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-h6fv-x4pg-r56c
Share
CVSS 9.8
CWE-125
Published
Advisory Summary

CVE-2026-68388 is a CRITICAL (CVSS 9.8) security vulnerability vulnerability (CWE-125: Out-of-bounds Read) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product reads data past the end, or before the beginning, of the intended buffer.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68388 at a Glance

CVE Identifier CVE-2026-68388
GHSA Identifier GHSA-h6fv-x4pg-r56c
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-125: Out-of-bounds Read
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.8

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

How to Fix CVE-2026-68388

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-68388, 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-125: Out-of-bounds Read, where the product reads data past the end, or before the beginning, of the intended buffer. 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: smb/client: handle overlapping allocated ranges in fallocate smb3_simple_fallocate_range() can skip holes when an allocated range returned by the server starts before the current fallocate offset. The skipped hole is not zero-filled, but fallocate still returns success. A later write to that hole may therefore fail with ENOSPC. The function queries allocated ranges so that it can preserve existing contents and write zeroes only into holes. However, the server may return a range that starts before the current fallocate offset. For example, assume the fallocate request is [100, 400) and the only allocated range returned by the server is [0, 200): Request: [100, 400) Server range: [ 0, 200) allocated Correct: [100, 200) allocated data, skip [200, 400) hole, zero-fill Current: [100, 300) skipped [300, 400) zero-filled afterwards The current code adds the full server range length, 200, to the current offset 100 and moves to 300. As a result, the hole in [200, 300) is skipped without being zero-filled. Fix this by advancing only over the part of the allocated range that overlaps the current fallocate offset. Ignore ranges that end before the current offset and reject ranges whose end offset overflows. This also prevents a malformed range length from causing an out-of-bounds zero-buffer read.

References

NVD — CVE-2026-68388 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68388
git.kernel.org/stable/c/0171988323... WEB
https://git.kernel.org/stable/c/01719883235507b1585e4c51e320d9a7113dc698
git.kernel.org/stable/c/377fe3e583... WEB
https://git.kernel.org/stable/c/377fe3e583e46369ee1004d5cfe12271d6589a68
git.kernel.org/stable/c/437637f5ff... WEB
https://git.kernel.org/stable/c/437637f5ff3f573b2edf8571de91fb00a21eb4e6
git.kernel.org/stable/c/7e08ab7a06... WEB
https://git.kernel.org/stable/c/7e08ab7a061b17ac1989a225c6afb53f44a86808
git.kernel.org/stable/c/a4a09e5142... WEB
https://git.kernel.org/stable/c/a4a09e5142835633fffbde68bd0a039ba4d4bf97
git.kernel.org/stable/c/aeb58a4eb3... WEB
https://git.kernel.org/stable/c/aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2
git.kernel.org/stable/c/b09ae45d85... WEB
https://git.kernel.org/stable/c/b09ae45d85dc816987a71db9eebc54b0ae288e94
git.kernel.org/stable/c/f47c7277c0... WEB
https://git.kernel.org/stable/c/f47c7277c03a636fcc3a57969f2dc09567b3c050

Frequently Asked Questions

What is CVE-2026-68388?
CVE-2026-68388 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-125: Out-of-bounds Read.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68388?
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-68388?
CVE-2026-68388 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-68388?
CVE-2026-68388 is classified under CWE-125: Out-of-bounds Read (The product reads data past the end, or before the beginning, of the intended buffer.).
How can I check Maven dependencies for CVE-2026-68388?
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-h6fv-x4pg-r56c",
  "modified" : "2026-08-19T18:32:17Z",
  "published" : "2026-08-10T15:33:49Z",
  "aliases" : [ "CVE-2026-68388" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsmb/client: handle overlapping allocated ranges in fallocate\n\nsmb3_simple_fallocate_range() can skip holes when an allocated range\nreturned by the server starts before the current fallocate offset. The\nskipped hole is not zero-filled, but fallocate still returns success. A\nlater write to that hole may therefore fail with ENOSPC.\n\nThe function queries allocated ranges so that it can preserve existing\ncontents and write zeroes only into holes. However, the server may return\na range that starts before the current fallocate offset.\n\nFor example, assume the fallocate request is [100, 400) and the only\nallocated range returned by the server is [0, 200):\n\n        Request:      [100, 400)\n        Server range: [  0, 200)  allocated\n\n        Correct:\n        [100, 200)    allocated data, skip\n        [200, 400)    hole, zero-fill\n\n        Current:\n        [100, 300)    skipped\n        [300, 400)    zero-filled afterwards\n\nThe current code adds the full server range length, 200, to the current\noffset 100 and moves to 300. As a result, the hole in [200, 300) is\nskipped without being zero-filled.\n\nFix this by advancing only over the part of the allocated range that\noverlaps the current fallocate offset.  Ignore ranges that end before the\ncurrent offset and reject ranges whose end offset overflows.\n\nThis also prevents a malformed range length from causing an out-of-bounds\nzero-buffer read.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68388"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/01719883235507b1585e4c51e320d9a7113dc698"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/377fe3e583e46369ee1004d5cfe12271d6589a68"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/437637f5ff3f573b2edf8571de91fb00a21eb4e6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7e08ab7a061b17ac1989a225c6afb53f44a86808"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a4a09e5142835633fffbde68bd0a039ba4d4bf97"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b09ae45d85dc816987a71db9eebc54b0ae288e94"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f47c7277c03a636fcc3a57969f2dc09567b3c050"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-125" ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:20:32Z"
  }
}