# CVE-2026-24826: Out-of-bounds write in turso3d

> An out-of-bounds write in the turso3d library allows attackers to execute arbitrary code or cause a denial of service.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** GHSA-9x3w-xc3m-rx49

## What is CVE-2026-24826?

CVE-2026-24826 is a critical memory corruption vulnerability in cadaver turso3d, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Out-of-bounds Write, Divide By Zero, NULL Pointer Dereference, Use of Uninitialized Resource, Out-of-bounds Read, Reachable Assertion vulnerability in cadaver turso3d.This issue affects .

Weakness: CWE-908 (Use of Uninitialized Resource), CWE-787 (Out-of-bounds Write), CWE-617 (Reachable Assertion), CWE-476 (NULL Pointer Dereference), CWE-369 (Divide By Zero), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-24826 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24826 is a critical memory corruption vulnerability in cadaver turso3d, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24826 in the wild and no public exploit code.

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

## Sources

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

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