CVE-2026-118375

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-28. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-111551 (ENISA EUVD) · GHSA-pmf8-m38j-h768 (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

llama.cpp b8841 before b11865 contains an out-of-bounds write vulnerability in the ggml-rpc RDMA transport rdma_recv() function that allows unauthenticated peers to overflow the rpc-server stack. Attackers advertising RDMA capabilities in the HELLO message can send up to 256 KiB into a 1-byte stack variable in rpc_serve_client(), crashing the server or potentially executing code.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 28, 2026

Last Modified

November 3, 2026

Advisory Details (6)

Auto-updated Oct 28, 2026
Patch available. Sources: github_commit, github_release, github_pr.
Web page

llama.cpp b8841 before b11865 Stack-based Buffer Overflow via ggml-rpc RDMA rdma_recv() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/llama-cpp-b8841-before-b11865-stack-based-buffer-overflow-via-ggml-rpc-rdma-rdma-recv
Web page

GitHub - ggml-org/llama.cpp: LLM inference in C/C++ · GitHub

https://github.com/ggml-org/llama.cpp
GitHub release Patch Available

b11865

Patch available: ggml-org/llama.cpp b11865 (pre-release)

https://github.com/ggml-org/llama.cpp/releases/tag/b11865
Web page

llama.cpp/ggml/src/ggml-rpc/transport.cpp at 620d2225cc436ab0b001e3200e590e3b286ef9ab · ggml-org/llama.cpp · GitHub

https://github.com/ggml-org/llama.cpp/blob/620d2225cc436ab0b001e3200e590e3b286ef9ab/ggml/src/ggml-rpc/transport.cpp#L510-L528
GitHub commit

commit 9a0fde9967fa (ggml-org/llama.cpp)

Fix landed in ggml-org/llama.cpp commit 9a0fde9967fa — awaiting tagged release

https://github.com/ggml-org/llama.cpp/commit/9a0fde9967fa1a35b6e5dd1f47e1a3648b6fecc1
GitHub pull request

rpc : add bounds check in rdma_recv

Fix merged in ggml-org/llama.cpp PR #30399 on 2026-10-24 — awaiting tagged release

https://github.com/ggml-org/llama.cpp/pull/30399

Vendor Advisories for CVE-2026-118375(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
llama.cpp10108+dfsg-1 ... 9951+dfsg-3 (63 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 24× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-11-11 03:44 UTCGHSA enrichmentGHSA-pmf8-m38j-h768 · GitHub severity CRITICAL · GitHub CVSS 8.1
  5. 2026-11-11 01:23 UTCEchelonGraph re-scored
  6. 2026-11-11 01:23 UTCGHSA enrichmentGHSA-pmf8-m38j-h768 · GitHub severity CRITICAL · GitHub CVSS 8.1
  7. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-11-03 20:13 UTCEchelonGraph re-scored
  14. 2026-11-03 20:13 UTCGHSA enrichmentGHSA-pmf8-m38j-h768 · GitHub severity CRITICAL · GitHub CVSS 8.1
  15. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-11-03 13:33 UTCEchelonGraph re-scored
  17. 2026-11-03 13:33 UTCGHSA enrichmentGHSA-pmf8-m38j-h768 · GitHub severity CRITICAL · GitHub CVSS 8.1
  18. 2026-11-03 12:54 UTCEchelonGraph re-scored
  19. 2026-11-03 12:54 UTCGHSA enrichmentGHSA-pmf8-m38j-h768 · GitHub severity CRITICAL · GitHub CVSS 8.1
  20. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Show 6 more
  1. 2026-10-28 15:26 UTCEchelonGraph re-scored
  2. 2026-10-28 15:26 UTCGHSA enrichmentGHSA-pmf8-m38j-h768 · GitHub severity CRITICAL · GitHub CVSS 8.1
  3. 2026-10-28 03:27 UTCEchelonGraph re-scored
  4. 2026-10-28 03:01 UTCENISA EUVD ID recordedEUVD-2026-111551 · Source: ENISA EUVD
  5. 2026-10-28 02:25 UTCEchelonGraph re-scoredFirst assessed: 8.1 HIGH
  6. 2026-10-28 02:24 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-118375?
CVE-2026-118375 is a high-severity vulnerability; its CVE record was published on October 28, 2026. llama.cpp b8841 before b11865 contains an out-of-bounds write vulnerability in the ggml-rpc RDMA transport rdma_recv() function that allows unauthenticated peers to overflow the rpc-server stack. Attackers advertising RDMA capabilities in the HELLO message can send up to 256 KiB into a 1-byte stack…
When was CVE-2026-118375 made public?
CVE-2026-118375 was made public on October 24, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 28, 2026. EchelonGraph's copy of the record carries a last-modified date of November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-118375 actively exploited?
CVE-2026-118375 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118375?
CVE-2026-118375 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-118375?
A fix for CVE-2026-118375 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-118375 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-118375

Explore →

Is Your Infrastructure Affected by CVE-2026-118375?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs