# CVE-2026-94049: 06ketan slideshot renderer.ts render_slides path traversal

> Remote attackers can exploit a path traversal flaw in the slideshot CLI renderer to read arbitrary files from the server.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-j3p4-767v-v66w

## What is CVE-2026-94049?

CVE-2026-94049 is a medium-severity path traversal vulnerability in 06ketan slideshot, published on 20 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in 06ketan slideshot up to 4.4.0. This impacts the function render_slides of the file packages/cli/src/renderer.ts. This manipulation of the argument htmlPath causes path traversal. The attack is possible to be carried out remotely. The exploit has been published and may be used. 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-94049?


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

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

## Is CVE-2026-94049 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94049 is a medium-severity path traversal vulnerability in 06ketan slideshot, published on 20 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-94049 exists.

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

## Sources

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

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