# CVE-2026-110695: turboderp ExLlamaV2 Safetensors Tensor Loader stloader.py STFile.get_tensor buffer overflow

> Remote attackers can trigger a buffer overflow in ExLlamaV2's Safetensors loader via manipulated data offsets, potentially leading to code execution or crashes.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-w755-fw26-6333

## What is CVE-2026-110695?

CVE-2026-110695 is a medium-severity memory corruption vulnerability in turboderp ExLlamaV2, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was detected in turboderp ExLlamaV2 up to 0.3.2. Affected is the function STFile.get_tensor of the file exllamav2/stloader.py of the component Safetensors Tensor Loader. Performing a manipulation of the argument data_offsets results in buffer overflow. The attack is possible to be carried out remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-110695?


## How do I fix CVE-2026-110695?

No fix has been published for CVE-2026-110695 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110695 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110695 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110695 and fix it if it is affected.

What it is: CVE-2026-110695 is a medium-severity memory corruption vulnerability in turboderp ExLlamaV2, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110695 exists.

Affected product: turboderp ExLlamaV2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110695/ (Markdown: https://insights.sbomify.com/CVE-2026-110695/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110695
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110695
- OSV: https://osv.dev/vulnerability/CVE-2026-110695

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110695/
Summaries are generated and may contain mistakes; the official description above is the record.
