CVE-2026-43408: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-97qv-cc94-mr6w
Share
CVSS 7.8
CWE-457 CWE-476
Published
Advisory Summary

CVE-2026-43408 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-457: Use of Uninitialized Variable) affecting Software libraries in the Maven ecosystem. The weakness occurs when the code uses a variable that has not been initialized, leading to unpredictable or unintended results.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-43408 at a Glance

CVE Identifier CVE-2026-43408
GHSA Identifier GHSA-97qv-cc94-mr6w
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification CWE-457: Use of Uninitialized Variable
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

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

How to Fix CVE-2026-43408

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-43408, 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-457: Use of Uninitialized Variable, where the code uses a variable that has not been initialized, leading to unpredictable or unintended results. 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: ceph: add a bunch of missing ceph_path_info initializers ceph_mdsc_build_path() must be called with a zero-initialized ceph_path_info parameter, or else the following ceph_mdsc_free_path_info() may crash. Example crash (on Linux 6.18.12): virt_to_cache: Object is not a Slab page! WARNING: CPU: 184 PID: 2871736 at mm/slub.c:6732 kmem_cache_free+0x316/0x400 [...] Call Trace: [...] ceph_open+0x13d/0x3e0 do_dentry_open+0x134/0x480 vfs_open+0x2a/0xe0 path_openat+0x9a3/0x1160 [...] cache_from_obj: Wrong slab cache. names_cache but object is from ceph_inode_info WARNING: CPU: 184 PID: 2871736 at mm/slub.c:6746 kmem_cache_free+0x2dd/0x400 [...] kernel BUG at mm/slub.c:634! Oops: invalid opcode: 0000 [#1] SMP NOPTI RIP: 0010:__slab_free+0x1a4/0x350 Some of the ceph_mdsc_build_path() callers had initializers, but others had not, even though they were all added by commit 15f519e9f883 ("ceph: fix race condition validating r_parent before applying state"). The ones without initializer are suspectible to random crashes. (I can imagine it could even be possible to exploit this bug to elevate privileges.) Unfortunately, these Ceph functions are undocumented and its semantics can only be derived from the code. I see that ceph_mdsc_build_path() initializes the structure only on success, but not on error. Calling ceph_mdsc_free_path_info() after a failed ceph_mdsc_build_path() call does not even make sense, but that's what all callers do, and for it to be safe, the structure must be zero-initialized. The least intrusive approach to fix this is therefore to add initializers everywhere.

References

NVD — CVE-2026-43408 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-43408
git.kernel.org/stable/c/43323a5934... WEB
https://git.kernel.org/stable/c/43323a5934b660afae687e8e4e95ac328615a5c4
git.kernel.org/stable/c/453df1f453... WEB
https://git.kernel.org/stable/c/453df1f4535842bf17ff1885a225e153d7ee3374
git.kernel.org/stable/c/644b47f057... WEB
https://git.kernel.org/stable/c/644b47f0574fd82aeb9d00317eca8d1f2a525c8c
git.kernel.org/stable/c/8be8911f59... WEB
https://git.kernel.org/stable/c/8be8911f590813e6f90bc6407ced1b23e50bc5da

Frequently Asked Questions

What is CVE-2026-43408?
CVE-2026-43408 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-457: Use of Uninitialized Variable.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-43408?
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-43408?
CVE-2026-43408 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-43408?
CVE-2026-43408 is classified under CWE-457: Use of Uninitialized Variable (The code uses a variable that has not been initialized, leading to unpredictable or unintended results.).
How can I check Maven dependencies for CVE-2026-43408?
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-97qv-cc94-mr6w",
  "modified" : "2026-05-11T09:30:31Z",
  "published" : "2026-05-08T15:31:27Z",
  "aliases" : [ "CVE-2026-43408" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nceph: add a bunch of missing ceph_path_info initializers\n\nceph_mdsc_build_path() must be called with a zero-initialized\nceph_path_info parameter, or else the following\nceph_mdsc_free_path_info() may crash.\n\nExample crash (on Linux 6.18.12):\n\n  virt_to_cache: Object is not a Slab page!\n  WARNING: CPU: 184 PID: 2871736 at mm/slub.c:6732 kmem_cache_free+0x316/0x400\n  [...]\n  Call Trace:\n   [...]\n   ceph_open+0x13d/0x3e0\n   do_dentry_open+0x134/0x480\n   vfs_open+0x2a/0xe0\n   path_openat+0x9a3/0x1160\n  [...]\n  cache_from_obj: Wrong slab cache. names_cache but object is from ceph_inode_info\n  WARNING: CPU: 184 PID: 2871736 at mm/slub.c:6746 kmem_cache_free+0x2dd/0x400\n  [...]\n  kernel BUG at mm/slub.c:634!\n  Oops: invalid opcode: 0000 [#1] SMP NOPTI\n  RIP: 0010:__slab_free+0x1a4/0x350\n\nSome of the ceph_mdsc_build_path() callers had initializers, but\nothers had not, even though they were all added by commit 15f519e9f883\n(\"ceph: fix race condition validating r_parent before applying state\").\nThe ones without initializer are suspectible to random crashes.  (I can\nimagine it could even be possible to exploit this bug to elevate\nprivileges.)\n\nUnfortunately, these Ceph functions are undocumented and its semantics\ncan only be derived from the code.  I see that ceph_mdsc_build_path()\ninitializes the structure only on success, but not on error.\n\nCalling ceph_mdsc_free_path_info() after a failed\nceph_mdsc_build_path() call does not even make sense, but that's what\nall callers do, and for it to be safe, the structure must be\nzero-initialized.  The least intrusive approach to fix this is\ntherefore to add initializers everywhere.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-43408"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/43323a5934b660afae687e8e4e95ac328615a5c4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/453df1f4535842bf17ff1885a225e153d7ee3374"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/644b47f0574fd82aeb9d00317eca8d1f2a525c8c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8be8911f590813e6f90bc6407ced1b23e50bc5da"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-457", "CWE-476" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-08T15:16:52Z"
  }
}