CVE-2026-43076: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-w594-5gj3-f9g6
Share
CVSS 7.8
CWE-416
Published
Advisory Summary

CVE-2026-43076 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-416: Use After Free) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product reuses or references memory after it has been freed. at some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-43076 at a Glance

CVE Identifier CVE-2026-43076
GHSA Identifier GHSA-w594-5gj3-f9g6
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification CWE-416: Use After Free
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:N/UI:R/S:U/C:H/I:H/A:H).

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

How to Fix CVE-2026-43076

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-43076, 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-416: Use After Free, where the product reuses or references memory after it has been freed. at some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. 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: ocfs2: validate inline data i_size during inode read When reading an inode from disk, ocfs2_validate_inode_block() performs various sanity checks but does not validate the size of inline data. If the filesystem is corrupted, an inode's i_size can exceed the actual inline data capacity (id_count). This causes ocfs2_dir_foreach_blk_id() to iterate beyond the inline data buffer, triggering a use-after-free when accessing directory entries from freed memory. In the syzbot report: - i_size was 1099511627576 bytes (~1TB) - Actual inline data capacity (id_count) is typically <256 bytes - A garbage rec_len (54648) caused ctx->pos to jump out of bounds - This triggered a UAF in ocfs2_check_dir_entry() Fix by adding a validation check in ocfs2_validate_inode_block() to ensure inodes with inline data have i_size <= id_count. This catches the corruption early during inode read and prevents all downstream code from operating on invalid data.

References

NVD — CVE-2026-43076 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-43076
git.kernel.org/stable/c/131c0b573e... WEB
https://git.kernel.org/stable/c/131c0b573e1b467b7d553e9ff38003f1acd8f5f2
git.kernel.org/stable/c/1524af3685... WEB
https://git.kernel.org/stable/c/1524af3685b35feac76662cc551cbc37bd14775f
git.kernel.org/stable/c/37f074e65f... WEB
https://git.kernel.org/stable/c/37f074e65f24f10f8d8df224a572e4cb9e6faf63
git.kernel.org/stable/c/77d0295725... WEB
https://git.kernel.org/stable/c/77d0295725109d77f5854ef5b58c0d06c08168cc
git.kernel.org/stable/c/bcd46bc261... WEB
https://git.kernel.org/stable/c/bcd46bc261b215b3b12c557a978299eafa02ecdd
git.kernel.org/stable/c/c1de19e891... WEB
https://git.kernel.org/stable/c/c1de19e891be3bfb3e1d0c7cf07bbb8fb3b77c1b
git.kernel.org/stable/c/cd2d765aa7... WEB
https://git.kernel.org/stable/c/cd2d765aa7157f852999842af32148128c735d39
git.kernel.org/stable/c/d012c782ab... WEB
https://git.kernel.org/stable/c/d012c782abcabe68b5b9e71be58a15e9f9d83dc1

Frequently Asked Questions

What is CVE-2026-43076?
CVE-2026-43076 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-416: Use After Free.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-43076?
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-43076?
CVE-2026-43076 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-43076?
CVE-2026-43076 is classified under CWE-416: Use After Free (The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.).
How can I check Maven dependencies for CVE-2026-43076?
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-w594-5gj3-f9g6",
  "modified" : "2026-06-01T18:31:29Z",
  "published" : "2026-05-06T12:30:26Z",
  "aliases" : [ "CVE-2026-43076" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: validate inline data i_size during inode read\n\nWhen reading an inode from disk, ocfs2_validate_inode_block() performs\nvarious sanity checks but does not validate the size of inline data.  If\nthe filesystem is corrupted, an inode's i_size can exceed the actual\ninline data capacity (id_count).\n\nThis causes ocfs2_dir_foreach_blk_id() to iterate beyond the inline data\nbuffer, triggering a use-after-free when accessing directory entries from\nfreed memory.\n\nIn the syzbot report:\n  - i_size was 1099511627576 bytes (~1TB)\n  - Actual inline data capacity (id_count) is typically <256 bytes\n  - A garbage rec_len (54648) caused ctx->pos to jump out of bounds\n  - This triggered a UAF in ocfs2_check_dir_entry()\n\nFix by adding a validation check in ocfs2_validate_inode_block() to ensure\ninodes with inline data have i_size <= id_count.  This catches the\ncorruption early during inode read and prevents all downstream code from\noperating on invalid data.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-43076"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/131c0b573e1b467b7d553e9ff38003f1acd8f5f2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1524af3685b35feac76662cc551cbc37bd14775f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/37f074e65f24f10f8d8df224a572e4cb9e6faf63"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/77d0295725109d77f5854ef5b58c0d06c08168cc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bcd46bc261b215b3b12c557a978299eafa02ecdd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c1de19e891be3bfb3e1d0c7cf07bbb8fb3b77c1b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cd2d765aa7157f852999842af32148128c735d39"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d012c782abcabe68b5b9e71be58a15e9f9d83dc1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-416" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-06T10:16:20Z"
  }
}