CVE Intelligence
Medium Memory corruption exploit reference

CVE-2026-116096 — ggml-org llama.cpp Pocket-TTS pockettts-gen.cpp list_pockettts_state_slots out-of-bounds write

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.

Published Oct 25, 2026 · Updated Oct 26, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: VulDB

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
  • EPSS 0.1% (30-day exploitation probability)+0
  • Technical severity (medium)+3
  • CISA SSVC: exploitation "poc"+5

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
0.12%
ahead of 2% of scored CVEs · Oct 26, 2026
Affects
Ggml-org
Llama.cpp
CVSS base
5.3
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

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. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Ggml-org Llama.cpp version 0.4.0version 0.17.1version 55abc39version 55d4206c8version b5693version b7445version b7824version b8492
and 3 more version b8585version b9058version b9060
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
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Every base score collected

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

ScoreVersionSeverityExpl.ImpactScored by
4.8 CVSS 4.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
1.9 CVSS 4.0 Low — — cna@vuldb.com via NIST National Vulnerability Database
5.3 CVSS 3.1 Medium 1.8 3.4 cna@vuldb.com via NIST National Vulnerability Database
5.3 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.3 CVSS 3.1 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.3 CVSS 3.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
4.3 CVSS 2.0 Medium 3.1 6.4 cna@vuldb.com via NIST National Vulnerability Database
4.3 CVSS 2.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-119 · Buffer Errors (Improper Restriction of Operations within Memory Bounds)

Other CVEs with this weakness →

Detection

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

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Received → Deferred
    Oct 26, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Received
    Oct 25, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 25, 2026
  • CVSS changed · 5.3
    Oct 25, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 25, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 25, 2026 · CVE Program (cve.org) e CISA ADP
  • CVE published
    Oct 25, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 26, 2026 – Oct 26, 2026
  • 1× Official description updated · Oct 25, 2026 – Oct 25, 2026

References

13 on the record

Elsewhere on this site

Ggml-org
every CVE for this vendor
Memory corruption
same class
CWE-119
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-116840 llama.cpp b5854 before b11275 Integer Overflow in gguf_init_from_reader 8h
  • CVE-2026-116816 llama.cpp b5899 before b10261 Heap Out-of-Bounds Write via plamo2 Tokenizer 8h
  • CVE-2026-116829 llama.cpp b10398 before b11301 Integer Overflow in gguf_init_from_reader 8h
  • CVE-2025-71439 llama.cpp before b5649 Heap Out-of-Bounds Read via llama_vocab::impl::print_info 8h
  • CVE-2024-58400 llama.cpp before b3701 Out-of-Bounds Read in llama_decode via Token IDs 8h
  • CVE-2024-58399 llama.cpp before b2731 Out-of-Bounds Read via GGUF Tensor Offsets 8h

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 fixed version, patch or mitigation documented.
  • 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-116096 is "ggml-org llama.cpp Pocket-TTS pockettts-gen.cpp list_pockettts_state_slots out-of-bounds write", rated Medium. 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 5.3 describes technical severity. EPSS 0.12% estimates the probability of exploitation in 30 days; neither replaces your asset context. 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.