CVE-2026-45912: Software Security Vulnerability Vulnerability

MODERATE

Advisory Identifier: GHSA-2r5x-f6hq-8f5p

CVSS 5.5

Published 2026-05-27

Advisory Summary

CVE-2026-45912 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-45912 at a Glance

CVE Identifier CVE-2026-45912

GHSA Identifier GHSA-2r5x-f6hq-8f5p

Severity MODERATE

CVSS v3.1 Base Score 5.5

CWE Classification General Security Weakness

Affected Product Software

Package Ecosystem Maven

Published Date 2026-05-27

Last Updated 2026-06-24

Security Impact

CVSS: 5.5

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:N/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 None (C:N)

Integrity None (I:N)

Availability High (A:H)

How to Fix CVE-2026-45912

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-45912, 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 General Security Weakness. 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: ext4: don't cache extent during splitting extent Caching extents during the splitting process is risky, as it may result in stale extents remaining in the status tree. Moreover, in most cases, the corresponding extent block entries are likely already cached before the split happens, making caching here not particularly useful. Assume we have an unwritten extent, and then DIO writes the first half. [UUUUUUUUUUUUUUUU] on-disk extent U: unwritten extent [UUUUUUUUUUUUUUUU] extent status tree |<- ->| ----> dio write this range First, when ext4_split_extent_at() splits this extent, it truncates the existing extent and then inserts a new one. During this process, this extent status entry may be shrunk, and calls to ext4_find_extent() and ext4_cache_extents() may occur, which could potentially insert the truncated range as a hole into the extent status tree. After the split is completed, this hole is not replaced with the correct status. [UUUUUUU|UUUUUUUU] on-disk extent U: unwritten extent [UUUUUUU|HHHHHHHH] extent status tree H: hole Then, the outer calling functions will not correct this remaining hole extent either. Finally, if we perform a delayed buffer write on this latter part, it will re-insert the delayed extent and cause an error in space accounting. In adition, if the unwritten extent cache is not shrunk during the splitting, ext4_cache_extents() also conflicts with existing extents when caching extents. In the future, we will add checks when caching extents, which will trigger a warning. Therefore, Do not cache extents that are being split.

References

NVD — CVE-2026-45912 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-45912

git.kernel.org/stable/c/4c2d9dac4d... WEB

https://git.kernel.org/stable/c/4c2d9dac4d328244f9365b0a1fa27ec802821820

git.kernel.org/stable/c/5b1f429045... WEB

https://git.kernel.org/stable/c/5b1f4290453314e11cd8e15c7baa8a9b76c19b23

git.kernel.org/stable/c/692103feca... WEB

https://git.kernel.org/stable/c/692103feca376ae4298c92aa8828015d20f1d87b

git.kernel.org/stable/c/8302b5b4aa... WEB

https://git.kernel.org/stable/c/8302b5b4aacdbb378f7b1216bb2ee782b5142415

git.kernel.org/stable/c/8b4b19a2f9... WEB

https://git.kernel.org/stable/c/8b4b19a2f96348d70bfa306ef7d4a13b0bcbea79

git.kernel.org/stable/c/93b2ebbbcb... WEB

https://git.kernel.org/stable/c/93b2ebbbcb2e63cfc21a1946dfe91d3aa7952036

git.kernel.org/stable/c/96007fd3c1... WEB

https://git.kernel.org/stable/c/96007fd3c106aea773c1afae2d6f64cceb6da208

git.kernel.org/stable/c/9a2b95cdaf... WEB

https://git.kernel.org/stable/c/9a2b95cdaf07785e2739199037bd9c0863ccc1be

Frequently Asked Questions

What is CVE-2026-45912?

CVE-2026-45912 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.

Which Software versions are affected?

Affected versions include releases prior to current release patches.

What version fixes CVE-2026-45912?

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-45912?

CVE-2026-45912 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

What CWE is associated with CVE-2026-45912?

CVE-2026-45912 is classified under General Security Weakness.

How can I check Maven dependencies for CVE-2026-45912?

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-2r5x-f6hq-8f5p",
  "modified" : "2026-06-24T15:31:40Z",
  "published" : "2026-05-27T15:33:16Z",
  "aliases" : [ "CVE-2026-45912" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\next4: don't cache extent during splitting extent\n\nCaching extents during the splitting process is risky, as it may result\nin stale extents remaining in the status tree. Moreover, in most cases,\nthe corresponding extent block entries are likely already cached before\nthe split happens, making caching here not particularly useful.\n\nAssume we have an unwritten extent, and then DIO writes the first half.\n\n  [UUUUUUUUUUUUUUUU] on-disk extent        U: unwritten extent\n  [UUUUUUUUUUUUUUUU] extent status tree\n  |<-   ->| ----> dio write this range\n\nFirst, when ext4_split_extent_at() splits this extent, it truncates the\nexisting extent and then inserts a new one. During this process, this\nextent status entry may be shrunk, and calls to ext4_find_extent() and\next4_cache_extents() may occur, which could potentially insert the\ntruncated range as a hole into the extent status tree. After the split\nis completed, this hole is not replaced with the correct status.\n\n  [UUUUUUU|UUUUUUUU] on-disk extent        U: unwritten extent\n  [UUUUUUU|HHHHHHHH] extent status tree    H: hole\n\nThen, the outer calling functions will not correct this remaining hole\nextent either. Finally, if we perform a delayed buffer write on this\nlatter part, it will re-insert the delayed extent and cause an error in\nspace accounting.\n\nIn adition, if the unwritten extent cache is not shrunk during the\nsplitting, ext4_cache_extents() also conflicts with existing extents\nwhen caching extents. In the future, we will add checks when caching\nextents, which will trigger a warning. Therefore, Do not cache extents\nthat are being split.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-45912"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4c2d9dac4d328244f9365b0a1fa27ec802821820"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5b1f4290453314e11cd8e15c7baa8a9b76c19b23"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/692103feca376ae4298c92aa8828015d20f1d87b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8302b5b4aacdbb378f7b1216bb2ee782b5142415"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8b4b19a2f96348d70bfa306ef7d4a13b0bcbea79"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/93b2ebbbcb2e63cfc21a1946dfe91d3aa7952036"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/96007fd3c106aea773c1afae2d6f64cceb6da208"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9a2b95cdaf07785e2739199037bd9c0863ccc1be"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-27T14:17:05Z"
  }
}

CVSS V3

5.5 MODERATE