CVE-2026-92525: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-xqgc-mf52-qvg8
Share
CVSS 7.1
Published
Advisory Summary

CVE-2026-92525 is a HIGH (CVSS 7.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-92525 at a Glance

CVE Identifier CVE-2026-92525
GHSA Identifier GHSA-xqgc-mf52-qvg8
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.1

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

How to Fix CVE-2026-92525

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-92525, 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/rxe: Validate num_sge/cur_sge before indexing wqe->dma.sge[] For a user QP, qp->sq.queue is a ring the application writes directly, so rxe_post_send() takes the is_user branch and only schedules send_task without validating the WQE. rxe_requester() consumes it in place via req_next_wqe() and calls copy_data(), which indexes &wqe->dma.sge[cur_sge] with the attacker-controlled num_sge/cur_sge. Only the kernel path bounds num_sge (validate_send_wr()); the user WQE is never checked, so a local unprivileged user can post a WQE with an out-of-range cur_sge or oversized num_sge and force an out-of-bounds read of the per-WQE sge array in copy_data() (vmalloc OOB read, local DoS). Bound num_sge to qp->sq.max_sge in rxe_requester() before use, the way get_srq_wqe() already guards SRQ entries, and bound cur_sge only when the WQE carries payload (dma.resid): copy_data() returns early on a zero-length copy before touching dma->sge[], so a zero-payload WQE -- the only kind a max_sge == 0 QP can post -- stays valid. Reproduced under KASAN; the vmalloc-out-of-bounds in copy_data() is gone.

References

NVD — CVE-2026-92525 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-92525
git.kernel.org/stable/c/126c757e4c... WEB
https://git.kernel.org/stable/c/126c757e4cd46f866ddc283143b58eb4d9bf52cd
git.kernel.org/stable/c/13cb7160e5... WEB
https://git.kernel.org/stable/c/13cb7160e5b791f5e3ecf9311cf32849fe7e9b62
git.kernel.org/stable/c/5ec111ddc1... WEB
https://git.kernel.org/stable/c/5ec111ddc1f727c1e4580aea459842ae5a8359a5
git.kernel.org/stable/c/69d3ccf654... WEB
https://git.kernel.org/stable/c/69d3ccf6543f24c452a020c8028ca6f46cb1e8db
git.kernel.org/stable/c/750bba6ce9... WEB
https://git.kernel.org/stable/c/750bba6ce9bb0b11d6a166031c9728ae3f21765e
git.kernel.org/stable/c/c067aa7b23... WEB
https://git.kernel.org/stable/c/c067aa7b231e91a18a1b3666201ab14dfb00347a

Frequently Asked Questions

What is CVE-2026-92525?
CVE-2026-92525 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-92525?
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-92525?
CVE-2026-92525 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H.
What CWE is associated with CVE-2026-92525?
CVE-2026-92525 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-92525?
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-xqgc-mf52-qvg8",
  "modified" : "2026-09-18T18:31:33Z",
  "published" : "2026-09-17T18:32:07Z",
  "aliases" : [ "CVE-2026-92525" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Validate num_sge/cur_sge before indexing wqe->dma.sge[]\n\nFor a user QP, qp->sq.queue is a ring the application writes directly,\nso rxe_post_send() takes the is_user branch and only schedules send_task\nwithout validating the WQE. rxe_requester() consumes it in place via\nreq_next_wqe() and calls copy_data(), which indexes\n&wqe->dma.sge[cur_sge] with the attacker-controlled num_sge/cur_sge.\nOnly the kernel path bounds num_sge (validate_send_wr()); the user WQE\nis never checked, so a local unprivileged user can post a WQE with an\nout-of-range cur_sge or oversized num_sge and force an out-of-bounds\nread of the per-WQE sge array in copy_data() (vmalloc OOB read, local\nDoS).\n\nBound num_sge to qp->sq.max_sge in rxe_requester() before use, the way\nget_srq_wqe() already guards SRQ entries, and bound cur_sge only when\nthe WQE carries payload (dma.resid): copy_data() returns early on a\nzero-length copy before touching dma->sge[], so a zero-payload WQE --\nthe only kind a max_sge == 0 QP can post -- stays valid.\n\nReproduced under KASAN; the vmalloc-out-of-bounds in copy_data() is gone.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-92525"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/126c757e4cd46f866ddc283143b58eb4d9bf52cd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/13cb7160e5b791f5e3ecf9311cf32849fe7e9b62"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5ec111ddc1f727c1e4580aea459842ae5a8359a5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/69d3ccf6543f24c452a020c8028ca6f46cb1e8db"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/750bba6ce9bb0b11d6a166031c9728ae3f21765e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c067aa7b231e91a18a1b3666201ab14dfb00347a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:55Z"
  }
}