CVE-2026-64269: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-ffxc-rc5x-r6rp
Share
CVSS 9.1
Published
Advisory Summary

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

CVE-2026-64269 at a Glance

CVE Identifier CVE-2026-64269
GHSA Identifier GHSA-ffxc-rc5x-r6rp
Severity CRITICAL
CVSS v3.1 Base Score 9.1
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.1

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

How to Fix CVE-2026-64269

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-64269, 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: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg When the server answers an RTRS READ, rdma_write_sg() builds the source scatter/gather entry for the IB_WR_RDMA_WRITE that returns data to the peer. Its length is taken directly from the wire descriptor: plist->length = le32_to_cpu(id->rd_msg->desc[0].len); rd_msg points into the chunk buffer that the remote peer filled via RDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() -> process_read()), so desc[0].len is attacker-controlled and, before this change, was only rejected when zero. The source address is the fixed chunk start (dma_addr[msg_id]) and the source lkey is the PD-wide local_dma_lkey, which is not tied to the chunk's MR mapping, so the verbs layer does not constrain the transfer length to max_chunk_size. msg_id and off are bounded against queue_depth and max_chunk_size in rtrs_srv_rdma_done(), but desc[0].len is a separate field that was not checked against the chunk size. A peer that advertises desc[0].len larger than max_chunk_size can make the posted RDMA write read past the chunk's mapped region. The resulting behaviour depends on the IOMMU configuration: with no IOMMU or in passthrough mode the read may extend into memory adjacent to the chunk and be returned to the peer, which can disclose host memory; with a translating IOMMU the out-of-range access is expected to fault and abort the connection. In either case the transfer exceeds what the protocol permits and is driven by a remote peer. Reject a descriptor length above max_chunk_size, mirroring the existing off >= max_chunk_size bound in rtrs_srv_rdma_done(). Legitimate clients do not exceed it: the client sets desc[0].len to its MR length, which is capped at the negotiated max_io_size (max_chunk_size - MAX_HDR_SIZE).

References

NVD — CVE-2026-64269 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-64269
git.kernel.org/stable/c/2912f3d403... WEB
https://git.kernel.org/stable/c/2912f3d40355dabc08fdbaaf2764d02445fe88dc
git.kernel.org/stable/c/5a45d0aa1f... WEB
https://git.kernel.org/stable/c/5a45d0aa1fa50a333ce5763ade744e2d89838667
git.kernel.org/stable/c/68c0976217... WEB
https://git.kernel.org/stable/c/68c09762172f6224e9ddf9b0a60bacbb36e443eb
git.kernel.org/stable/c/6cada54015... WEB
https://git.kernel.org/stable/c/6cada540150894e81042a0ae0c796a21a9a877da
git.kernel.org/stable/c/6f40246f43... WEB
https://git.kernel.org/stable/c/6f40246f4312fdbab5a13cc440adebf95eb2aa66
git.kernel.org/stable/c/963af8d97a... WEB
https://git.kernel.org/stable/c/963af8d97a8c6a117134a8d0db1415e0489200b1
git.kernel.org/stable/c/a35b7a8728... WEB
https://git.kernel.org/stable/c/a35b7a8728a53ddc80b323970689fa5985816836
git.kernel.org/stable/c/da3e44add9... WEB
https://git.kernel.org/stable/c/da3e44add94b05dfde56f898421922f5cf35705f

Frequently Asked Questions

What is CVE-2026-64269?
CVE-2026-64269 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-64269?
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-64269?
CVE-2026-64269 has a CVSS v3.1 base score of 9.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H.
What CWE is associated with CVE-2026-64269?
CVE-2026-64269 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-64269?
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-ffxc-rc5x-r6rp",
  "modified" : "2026-08-23T15:32:55Z",
  "published" : "2026-07-25T12:31:28Z",
  "aliases" : [ "CVE-2026-64269" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg\n\nWhen the server answers an RTRS READ, rdma_write_sg() builds the source\nscatter/gather entry for the IB_WR_RDMA_WRITE that returns data to the\npeer. Its length is taken directly from the wire descriptor:\n\n  plist->length = le32_to_cpu(id->rd_msg->desc[0].len);\n\nrd_msg points into the chunk buffer that the remote peer filled via\nRDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() ->\nprocess_read()), so desc[0].len is attacker-controlled and, before this\nchange, was only rejected when zero. The source address is the fixed\nchunk start (dma_addr[msg_id]) and the source lkey is the PD-wide\nlocal_dma_lkey, which is not tied to the chunk's MR mapping, so the verbs\nlayer does not constrain the transfer length to max_chunk_size. msg_id\nand off are bounded against queue_depth and max_chunk_size in\nrtrs_srv_rdma_done(), but desc[0].len is a separate field that was not\nchecked against the chunk size.\n\nA peer that advertises desc[0].len larger than max_chunk_size can make\nthe posted RDMA write read past the chunk's mapped region. The resulting\nbehaviour depends on the IOMMU configuration: with no IOMMU or in\npassthrough mode the read may extend into memory adjacent to the chunk\nand be returned to the peer, which can disclose host memory; with a\ntranslating IOMMU the out-of-range access is expected to fault and abort\nthe connection. In either case the transfer exceeds what the protocol\npermits and is driven by a remote peer.\n\nReject a descriptor length above max_chunk_size, mirroring the existing\noff >= max_chunk_size bound in rtrs_srv_rdma_done(). Legitimate clients\ndo not exceed it: the client sets desc[0].len to its MR length, which is\ncapped at the negotiated max_io_size (max_chunk_size - MAX_HDR_SIZE).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64269"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2912f3d40355dabc08fdbaaf2764d02445fe88dc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5a45d0aa1fa50a333ce5763ade744e2d89838667"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/68c09762172f6224e9ddf9b0a60bacbb36e443eb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6cada540150894e81042a0ae0c796a21a9a877da"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6f40246f4312fdbab5a13cc440adebf95eb2aa66"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/963af8d97a8c6a117134a8d0db1415e0489200b1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a35b7a8728a53ddc80b323970689fa5985816836"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/da3e44add94b05dfde56f898421922f5cf35705f"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-25T10:17:07Z"
  }
}