Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-116096Published 2026-10-25

CVE-2026-116096 — ggml-org llama.cpp

medium

As of 2026-10-26, CVE-2026-116096 is a MEDIUM-severity vulnerability in ggml-org llama.cpp, CVSS v3.1 5.3, EPSS 0.1% (2.1th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-116096 as of 2026-10-26; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
5.3/10Medium
EPSS
0.1%Higher than 2.1% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
2.7/10Threadlinqs triage score
Published
Updated 2026-10-26
CVSS v3.1 5.3 (MEDIUM) · CVSS v4.0 4.8 · EPSS 0.1% (higher than 2.1% of all scored CVEs) · Priority 2.7/10 · Published 2026-10-25

Last updated:

What is CVE-2026-116096?

A weakness has been identified in ggml-org llama.cpp. Affected by this issue is the function list_pockettts_state_slots of the file tools/mtmd/models/pockettts-gen.cpp of the component Pocket-TTS. This manipulation of the argument mmproj causes out-of-bounds write. The attack requires local access. The exploit has been made available to the public and could be used for attacks. Upgrading to version b11796 can resolve this issue. Patch name: 0a1ef309cdbb9f2024f58a38fb4c42352c5db569. The affected component should be upgraded. The reported heap out‑of‑bounds write (gen‑audio / pocket‑tts state_out path) is no longer a silent exploitable heap write on current master and the latest release b11871 - a malicious mmproj that previously triggered it now trips a release‑active GGML_ASSERT and aborts. But the submitter's recommended by‑construction fix (PR #29360 "prevent OOB accesses from malformed mmproj files") is still open. So the root cause is detected‑and‑aborted, not prevented‑by‑design.

The record classifies CVE-2026-116096 under weakness classes CWE-787, CWE-119. Its CVSS v3 base vector states that the flaw requires local access to the host, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 25 days ago.

Severity and exploitation probability

CVSS v3.1 base score
5.3 — MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C
CVSS v4.0 base score
4.8
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 2.1% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
2.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-10-25

Is CVE-2026-116096 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

Affected products and versions

  • ggml-org: llama.cpp

How to fix CVE-2026-116096

Patch reference: https://github.com/ggml-org/llama.cpp/pull/30902. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-116096

No threat campaign in the Threadlinqs corpus currently references CVE-2026-116096, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, GitHub Security Advisories, FIRST EPSS.

Vendor advisory and patch

Exploit and proof of concept

Technical analysis

Third-party advisory

Issue tracking and product pages