CVE Intelligence
High

CVE-2026-119052 — llama.cpp b2877 before b11935 ggml-rpc Server DoS via Oversized recv_msg Length

llama.cpp b2877 before b11935 contains an uncaught exception vulnerability in the ggml-rpc server that allows unauthenticated remote attackers to crash the rpc-server by sending oversized message lengths. After the HELLO handshake, attackers can send a command such as SET_TENSOR with a length above std::vector::max_size(), triggering an uncaught std::length_error that aborts the process and denies service to all clients.

Published Oct 29, 2026 · Updated Oct 29, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Ggml-org
Llama.cpp
CVSS base
7.5
High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Ggml-org Llama.cpp).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Ggml-org Llama.cpp ≥ b2877 and < b11935 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.7 CVSS 4.0 High — — disclosure@vulncheck.com via NIST National Vulnerability Database
8.7 CVSS 4.0 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
7.5 CVSS 3.1 High 3.9 3.6 disclosure@vulncheck.com via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-248

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · ggml-org/llama.cpp
    Oct 29, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 29, 2026
  • CVSS changed · 7.5
    Oct 29, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 29, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 29, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 29, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 29, 2026 – Oct 29, 2026

References

6 on the record

Elsewhere on this site

Ggml-org
every CVE for this vendor
CWE-248
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-118375 llama.cpp b8841 before b11865 Stack-based Buffer Overflow via ggml-rpc RDMA rdma_recv() 1d
  • Medium CVE-2026-116840 llama.cpp b5854 before b11275 Integer Overflow in gguf_init_from_reader 2d
  • High CVE-2026-116816 llama.cpp b5899 before b10261 Heap Out-of-Bounds Write via plamo2 Tokenizer 2d
  • Medium CVE-2026-116829 llama.cpp b10398 before b11301 Integer Overflow in gguf_init_from_reader 2d
  • Medium CVE-2025-71439 llama.cpp before b5649 Heap Out-of-Bounds Read via llama_vocab::impl::print_info 2d
  • High CVE-2024-58400 llama.cpp before b3701 Out-of-Bounds Read in llama_decode via Token IDs 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-119052 is "llama.cpp b2877 before b11935 ggml-rpc Server DoS via Oversized recv_msg Length", rated High. It affects Llama.cpp (Ggml-org); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.