# CVE-2026-49290: Slopsmith has path traversal in archive extractors that allows arbitrary file write → potential RCE

> Attackers can write arbitrary files via crafted archives, potentially achieving remote code execution on the host.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2026
- **Updated:** 22 Jun 2026

## What is CVE-2026-49290?

CVE-2026-49290 is a high-severity path traversal vulnerability in byrongamatos slopsmith, published on 19 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Slopsmith is a self-contained web application for browsing, playing, and practicing Rocksmith 2014 Custom DLC (CDLC). Prior to 0.2.9-alpha.5, a path-traversal vulnerability in Slopsmith's archive extractors allows an attacker to write arbitrary files outside the extraction directory by supplying a crafted PSARC or sloppak archive. With the default Docker configuration (running as root) and the ability to drop a file into the plugin directory, this escalates to arbitrary remote code execution on the host. Three archive extractors concatenated archive-entry filenames directly onto the extraction root without validation: `lib/psarc.py::unpack_psarc` — PSARC TOC filenames; `lib/patcher.py::unpack_psarc` — duplicate of the above in the patcher flow; `lib/sloppak.py::_unpack_zip` — bare `ZipFile.extractall()` with no member filter. Each accepts entry names containing `..` segments, absolute paths, or backslash separators. The Python `zipfile` module's default `extractall()` is documented as not preventing traversal when callers don't supply a member-filter callback. Version 0.2.9-alpha.5 patches the issue. Until updated, do not open PSARC or sloppak archives from untrusted sources, and do not expose the Slopsmith instance to the public internet. Docker users should also pull the latest image after the next slopsmith Docker image is published.

Weakness: CWE-36 (Absolute Path Traversal), CWE-23 (Relative Path Traversal), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-49290 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49290 is a high-severity path traversal vulnerability in byrongamatos slopsmith, published on 19 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49290 in the wild and no public exploit code.

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

## Sources

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

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