# CVE-2026-113352: uTox through 0.18.1 Path Traversal via Auto-Accepted File Transfers


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-113352, GHSA-pqrg-92p8-w72h, UBUNTU-CVE-2026-113352

## What is CVE-2026-113352?

CVE-2026-113352 is a high-severity vulnerability in uTox, published on 20 Oct 2026. 

### Official description

uTox through 0.18.1 contains a path traversal vulnerability that allows Tox friends to write arbitrary files by sending absolute or ../ file names to victims with auto-accept enabled. Attackers can overwrite shell startup files or plant crafted .ftinfo resume records that ft_find_resumeable() loads, abusing FILE pointers to write /proc/self/mem and execute code.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-113352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113352 is a high-severity vulnerability in uTox, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113352 in the wild and no public exploit code.

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

## Sources

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

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