CVE-2026-68131: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-rwc8-9546-9gw5
Share
CVSS 7.5
CWE-20
Published
Advisory Summary

CVE-2026-68131 is a HIGH (CVSS 7.5) security vulnerability vulnerability (CWE-20: Improper Input Validation) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68131 at a Glance

CVE Identifier CVE-2026-68131
GHSA Identifier GHSA-rwc8-9546-9gw5
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-20: Improper Input Validation
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

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

How to Fix CVE-2026-68131

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-68131, 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-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. 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: rbd: Reset positive result codes to zero in object map update path In a reply message to an RBD request, a positive result code indicates a data payload, which is not allowed for writes. While rbd_osd_req_callback() already resets a positive result code for writes to zero, rbd_object_map_callback() does not. This allows a corrupted reply to an object map update to trigger the rbd_assert(*result < 0) in __rbd_obj_handle_request(). This happens, because rbd_object_map_callback() calls rbd_obj_handle_request() -> __rbd_obj_handle_request() and passes this positive result code. From __rbd_obj_handle_request(), rbd_obj_advance_write() is called, which leaves the positive result code unchanged and returns true. Therefore, the if(done && *result) branch is executed in __rbd_obj_handle_request() and the assertion triggers. This patch fixes the issue by adjusting the logic in the rbd_object_map_callback() path. A positive result code for an object map update is now reset to zero (similar to rbd_osd_req_callback()), and the message is subsequently handled the same way as if the result code was zero from the beginning. Additionally, a WARN_ON_ONCE() is added for this case.

References

NVD — CVE-2026-68131 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68131
git.kernel.org/stable/c/14995c4250... WEB
https://git.kernel.org/stable/c/14995c4250f04b58bf6fc00e0e973a2e1b3cfb9b
git.kernel.org/stable/c/2419aa7408... WEB
https://git.kernel.org/stable/c/2419aa74081007dc4d14ff5640659052dfdfd69a
git.kernel.org/stable/c/34f2a2f32a... WEB
https://git.kernel.org/stable/c/34f2a2f32af570dfcc532ad70c080629ee1c32b0
git.kernel.org/stable/c/6f33d9d539... WEB
https://git.kernel.org/stable/c/6f33d9d539fb94e5a17589c2dfe271ff9bb64904
git.kernel.org/stable/c/a6c4250b81... WEB
https://git.kernel.org/stable/c/a6c4250b81bd30beae94e1b7a4b26fa1193ad2e4
git.kernel.org/stable/c/b1a6136693... WEB
https://git.kernel.org/stable/c/b1a61366933224b3ad80975c4d01ac2cc6931ecf
git.kernel.org/stable/c/cf1167292f... WEB
https://git.kernel.org/stable/c/cf1167292f606deaddac35ec384eba48f08a68d2
git.kernel.org/stable/c/da926959bf... WEB
https://git.kernel.org/stable/c/da926959bf791441ba06a80571708c3d0d3cc08f

Frequently Asked Questions

What is CVE-2026-68131?
CVE-2026-68131 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-20: Improper Input Validation.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68131?
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-68131?
CVE-2026-68131 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-68131?
CVE-2026-68131 is classified under CWE-20: Improper Input Validation (The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.).
How can I check Maven dependencies for CVE-2026-68131?
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-rwc8-9546-9gw5",
  "modified" : "2026-08-19T18:32:06Z",
  "published" : "2026-08-10T15:33:37Z",
  "aliases" : [ "CVE-2026-68131" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nrbd: Reset positive result codes to zero in object map update path\n\nIn a reply message to an RBD request, a positive result code indicates\na data payload, which is not allowed for writes. While\nrbd_osd_req_callback() already resets a positive result code for writes\nto zero, rbd_object_map_callback() does not. This allows a corrupted\nreply to an object map update to trigger the rbd_assert(*result < 0) in\n__rbd_obj_handle_request(). This happens, because\nrbd_object_map_callback() calls rbd_obj_handle_request() ->\n__rbd_obj_handle_request() and passes this positive result code. From\n__rbd_obj_handle_request(), rbd_obj_advance_write() is called, which\nleaves the positive result code unchanged and returns true. Therefore,\nthe if(done && *result) branch is executed in __rbd_obj_handle_request()\nand the assertion triggers.\n\nThis patch fixes the issue by adjusting the logic in the\nrbd_object_map_callback() path. A positive result code for an object map\nupdate is now reset to zero (similar to rbd_osd_req_callback()), and the\nmessage is subsequently handled the same way as if the result code was\nzero from the beginning. Additionally, a WARN_ON_ONCE() is added for\nthis case.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68131"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/14995c4250f04b58bf6fc00e0e973a2e1b3cfb9b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2419aa74081007dc4d14ff5640659052dfdfd69a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/34f2a2f32af570dfcc532ad70c080629ee1c32b0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6f33d9d539fb94e5a17589c2dfe271ff9bb64904"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a6c4250b81bd30beae94e1b7a4b26fa1193ad2e4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b1a61366933224b3ad80975c4d01ac2cc6931ecf"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cf1167292f606deaddac35ec384eba48f08a68d2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/da926959bf791441ba06a80571708c3d0d3cc08f"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:19:58Z"
  }
}