# CVE-2026-116502: turboderp-org ExLlamaV2 GPTQ Index q_matrix.cu make_sequential out-of-bounds write


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-56qq-ww5r-ph3r

## What is CVE-2026-116502?

CVE-2026-116502 is a medium-severity vulnerability in turboderp-org ExLlamaV2, published on 26 Oct 2026. 

### Official description

A flaw has been found in turboderp-org ExLlamaV2 up to 0.3.2. The impacted element is the function QMatrix::make_sequential of the file exllamav2/exllamav2_ext/cuda/q_matrix.cu of the component GPTQ Index Handler. Executing a manipulation of the argument g_idx can lead to out-of-bounds write. The attack needs to be launched locally. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-116502 being exploited?

There is no known exploitation of CVE-2026-116502 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116502 is a medium-severity vulnerability in turboderp-org ExLlamaV2, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116502 in the wild and no public exploit code.

Affected product: turboderp-org 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-116502/ (Markdown: https://insights.sbomify.com/CVE-2026-116502/index.md)
```

## Sources

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

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