# CVE-2026-111618: CoAI through 4.0.0 Unauthenticated Path Traversal via Archive Download Endpoints

> Unauthenticated attackers can exploit path traversal in archive download endpoints to read arbitrary files, including other users' data.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-r2h8-g3f5-9cw2

## What is CVE-2026-111618?

CVE-2026-111618 is a medium-severity path traversal vulnerability in coaidev CoAI, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CoAI (Chat Nio) through 4.0.0 contains an unauthenticated path traversal vulnerability in the generation and article archive download endpoints via the hash query parameter. Attackers can supply ../ sequences in hash to download any readable .tar.gz or .zip file, including other users' generated archives.

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

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


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

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

## Is CVE-2026-111618 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111618 is a medium-severity path traversal vulnerability in coaidev CoAI, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111618 exists.

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

## Sources

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

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