Severity by source
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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit requires a local user to open an attacker-supplied archive (AV:L, UI:R, PR:N); successful write escapes the container to the host, justifying scope change and full CIA impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
3DescriptionCVE.org
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.
Articles & Coverage 1
AnalysisAI
Arbitrary file write via path traversal in Slopsmith (a self-hosted Rocksmith 2014 CDLC web app) prior to 0.2.9-alpha.5 allows an attacker who can supply a malicious PSARC or sloppak archive to write files outside the extraction directory, escalating to remote code execution under the default Docker image which runs as root and exposes a writable plugin directory. The CVSS 4.0 vector reports high privileges required (PR:H), reflecting that the attacker must reach the archive-upload/open functionality of an authenticated user. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Technical ContextAI
Slopsmith is a Python web application that unpacks two custom container formats - Sony's PSARC archive used by Rocksmith 2014 and the project's own ZIP-based 'sloppak' format. Three extractors (lib/psarc.py::unpack_psarc, lib/patcher.py::unpack_psarc, and lib/sloppak.py::_unpack_zip) build destination paths by concatenating archive-entry filenames directly onto the extraction root with no normalization, no prefix check, and - in the sloppak case - a bare ZipFile.extractall() call. This is a textbook CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) flaw, and matches the Python documentation's explicit warning that zipfile.extractall() does not guard against traversal unless the caller supplies a member-filter callback. Entry names with '..' segments, absolute paths, or backslash separators all escape the intended directory, and the supplied CPE (cpe:2.3:a:byrongamatos:slopsmith:*) confirms all versions of the byrongamatos/slopsmith product are in scope until 0.2.9-alpha.5.
RemediationAI
Upgrade to Slopsmith 0.2.9-alpha.5 or later, which adds path validation to the PSARC and sloppak extractors (commit 9cccac12a, advisory GHSA-8wr9-348x-xwmr). Docker users should pull the latest published slopsmith image once it is built and, regardless of patch level, reconfigure the container to run as a non-root user and mount the plugin directory read-only where feasible - both reduce blast radius if a similar bug recurs. Until you can patch, do not open PSARC or sloppak archives from untrusted sources (community CDLC repositories, Discord drops, random forum links), keep the Slopsmith instance off the public internet and behind LAN-only access controls, and consider running it inside a rootless container or a dedicated unprivileged user account; the trade-off is that file ownership on bind-mounted plugin/CDLC directories may need adjustment.
Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t
BentoML version 1.4.2 and earlier contains an unauthenticated remote code execution vulnerability through insecure deser
pgAdmin 4 contains critical remote code execution vulnerabilities in the Query Tool download and Cloud Deployment endpoi
The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python
BentoML is a Python library for building online serving systems optimized for AI apps and model inference. Rated critica
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
pyLoad download manager version prior to 0.5.0b3.dev77 exposes the Flask SECRET_KEY through an unauthenticated endpoint.
Langflow (a visual LLM pipeline builder) contains a critical unauthenticated code execution vulnerability (CVE-2026-3301
In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and conse
Unauthenticated remote code execution affects Kestra OSS (the open-source event-driven orchestration platform) prior to
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
pyLoad is the free and open-source Download Manager written in pure Python. Rated medium severity (CVSS 5.3), this vulne
Same weakness CWE-22 – Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-38056