CVE-2026-64368: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-m4hc-cp9r-f6rj
Share
CVSS 8.1
CWE-665
Published
Advisory Summary

CVE-2026-64368 is a HIGH (CVSS 8.1) security vulnerability vulnerability (CWE-665: Improper Initialization) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-64368 at a Glance

CVE Identifier CVE-2026-64368
GHSA Identifier GHSA-m4hc-cp9r-f6rj
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-665: Improper Initialization
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.1

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

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
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-64368

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-64368, 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-665: Improper Initialization, where the product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. 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: mm/slab: do not limit zeroing to orig_size when only red zoning is enabled When init (zeroing) on allocation is requested, for kmalloc() we generally have to zero the full object size even if a smaller size is requested, in order to provide krealloc()'s __GFP_ZERO guarantees. But if we track the requested size, krealloc() uses that information to do the right thing, so we can zero only the requested size. With red zoning also enabled, any extra size became part of the red zone, so it must not be zeroed and thus we must zero only the requested size. However the current check is imprecise, and will trigger also when only SLAB_RED_ZONE is enabled without SLAB_STORE_USER (which enables tracking the requested size). This means enabling red zoning alone can compromise krealloc()'s __GFP_ZERO contract. Fix this by using slub_debug_orig_size() instead, which is the exact check for whether the requested size is tracked. We don't need to care if red zoning is also enabled or not. Also update and expand the comment accordingly.

References

NVD — CVE-2026-64368 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-64368
git.kernel.org/stable/c/0d18ccef14... WEB
https://git.kernel.org/stable/c/0d18ccef142f04433dfb2a0c120cf223d2b8a42c
git.kernel.org/stable/c/2382971aaa... WEB
https://git.kernel.org/stable/c/2382971aaaef5bf85a651234c64906f59580b8be
git.kernel.org/stable/c/6256899c3a... WEB
https://git.kernel.org/stable/c/6256899c3a34674bba6076884aedbba49fc695e4
git.kernel.org/stable/c/648927ceb8... WEB
https://git.kernel.org/stable/c/648927ceb84021a25a0fbd5673740956f318d534
git.kernel.org/stable/c/7e706d50fa... WEB
https://git.kernel.org/stable/c/7e706d50fa119eead6376bf0ef973e8d73a96030

Frequently Asked Questions

What is CVE-2026-64368?
CVE-2026-64368 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-665: Improper Initialization.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-64368?
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-64368?
CVE-2026-64368 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-64368?
CVE-2026-64368 is classified under CWE-665: Improper Initialization (The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.).
How can I check Maven dependencies for CVE-2026-64368?
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-m4hc-cp9r-f6rj",
  "modified" : "2026-07-27T06:30:34Z",
  "published" : "2026-07-25T12:31:33Z",
  "aliases" : [ "CVE-2026-64368" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/slab: do not limit zeroing to orig_size when only red zoning is enabled\n\nWhen init (zeroing) on allocation is requested, for kmalloc() we\ngenerally have to zero the full object size even if a smaller size is\nrequested, in order to provide krealloc()'s __GFP_ZERO guarantees.\n\nBut if we track the requested size, krealloc() uses that information to\ndo the right thing, so we can zero only the requested size. With red\nzoning also enabled, any extra size became part of the red zone, so it\nmust not be zeroed and thus we must zero only the requested size.\n\nHowever the current check is imprecise, and will trigger also when only\nSLAB_RED_ZONE is enabled without SLAB_STORE_USER (which enables tracking\nthe requested size). This means enabling red zoning alone can compromise\nkrealloc()'s __GFP_ZERO contract.\n\nFix this by using slub_debug_orig_size() instead, which is the exact\ncheck for whether the requested size is tracked. We don't need to care\nif red zoning is also enabled or not. Also update and expand the\ncomment accordingly.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/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-64368"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0d18ccef142f04433dfb2a0c120cf223d2b8a42c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2382971aaaef5bf85a651234c64906f59580b8be"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6256899c3a34674bba6076884aedbba49fc695e4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/648927ceb84021a25a0fbd5673740956f318d534"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7e706d50fa119eead6376bf0ef973e8d73a96030"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-665" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-25T10:17:19Z"
  }
}