# CVE-2026-122159: Edge0-AI Audio8_TTS Model Path Resolution runtime.py ArkTtsRuntime.__init__ path traversal


- **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
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-w3m8-v566-4538

## What is CVE-2026-122159?

CVE-2026-122159 is a medium-severity vulnerability in Edge0-AI Audio8_TTS, published on 5 Nov 2026. 

### Official description

A weakness has been identified in Edge0-AI Audio8_TTS up to 1d64afcc2da56222b41ddcf53de7b8bc54be1fb6. This affects the function ArkTtsRuntime.__init__ of the file onnx_runtime_0_1b_int8/arktts_runtime/runtime.py of the component Model Path Resolution. Executing a manipulation of the argument slow_decode_models can lead to path traversal. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2026-122159 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122159 is a medium-severity vulnerability in Edge0-AI Audio8_TTS, published on 5 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122159 exists.

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

## Sources

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

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