Skip to main content

CVE-2026-124994Turboderp-org ExLlamaV3 out-of-bounds read

Low priorityLow2.1EPSS not scored yet

CVE-2026-124994 is a out-of-bounds read in Turboderp-org ExLlamaV3, rated low (2.1 on CVSS 4.0).

Why this priority: Low severity, with no exploitation signal.

Published · Updated · NVD status: Deferred

What it is

Code reads past the end of a buffer, leaking memory contents or crashing. Code reads or writes outside the memory it was given, which can corrupt the process.

How it is reached

An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link.

What an attacker gains

The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker crash the process, read memory, or in the worst case run code.

Is it being exploited?

CISA's SSVC assessment notes a public proof of concept.

What to do

  1. Upgrade Turboderp-org ExLlamaV3 to 1.6.4 or later.
  2. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
  3. Warn the people who use it, and filter files and links on the way in.

Description from NVD

A security flaw has been discovered in Turboderp-org ExLlamaV3 up to 1.6.3. The affected element is the function ngram_dequant of the file exllamav3/exllamav3_ext/ngram.cu of the component NGramEmbedding. The manipulation of the argument head_bias results in out-of-bounds read. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 1.6.4 is sufficient to fix this issue. The patch is identified as c9a57ae832a3035e264e0a412e1daf4ebb699b98. It is suggested to upgrade the affected component.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Native code: operating systems, browsers and firmware. The flaw sits wherever native code reads untrusted data.
  • Network appliances and media or file parsers. The flaw sits wherever native code reads untrusted data.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • Wherever native code reads untrusted data. An attacker who crosses it can crash the process, read memory, or in the worst case run code.

Questions to answer about your own systems

  • Where does Turboderp-org ExLlamaV3 run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.