CVE-2026-118375

validatingZero is analyzing and reversing it now.

GHSA-pmf8-m38j-h768 ↗EUVD-2026-111551 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
ggml-org llama.cpp >= b8841, < b11865
fixed in b11865
CWE-787 Out-of-bounds Write
ETK-2026-2822Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 16mrunning
differential validationcurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0hvalidating
0
+1h
+2h
+3h

description

llama.cpp versions b8841 through before b11865 are affected in the ggml-rpc RDMA transport. An unauthenticated peer able to connect to the RPC service and advertise RDMA capability may crash the server or potentially execute code.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade llama.cpp to b11865 or later. Until upgraded, restrict access to the RPC service to trusted peers and disable or avoid exposing its RDMA transport where possible.

fixed in b11865

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-28 02:03Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-28 02:03Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-118375

{
  "etk_id": "ETK-2026-2822",
  "cve_id": "CVE-2026-118375",
  "display_id": "CVE-2026-118375",
  "ghsa_id": "GHSA-pmf8-m38j-h768",
  "euvd_id": "EUVD-2026-111551",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Out-of-bounds write in llama.cpp ggml-rpc RDMA transport",
  "summary": "llama.cpp versions b8841 through before b11865 are affected in the ggml-rpc RDMA transport. An unauthenticated peer able to connect to the RPC service and advertise RDMA capability may crash the server or potentially execute code.",
  "mitigation": "Upgrade llama.cpp to b11865 or later. Until upgraded, restrict access to the RPC service to trusted peers and disable or avoid exposing its RDMA transport where possible.",
  "vendor": "ggml-org",
  "product": "llama.cpp",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= b8841, < b11865"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "b11865"
      ],
      "package_name": "llama.cpp",
      "purl": null
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 32.46359546666667,
  "t0_at": "2026-10-28T02:03:22.895000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T02:03:22.895000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T02:03:22.895000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-118375"
    }
  }
}

published 2026-10-28 02:33Z
last change 2026-10-28 05:09Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.