CVE-2026-49290 byrongamatos CVE debrief

Who should care

Defenders managing Slopsmith instances, particularly those exposed to the public internet or running with elevated privileges (e.g., root), should prioritize patching to version 0.2.9-alpha.5. Docker users should pull the latest image once it's available. All users of Slopsmith should be cautious when handling PSARC or sloppak archives from untrusted sources.

Technical summary

The vulnerability exists in three archive extractors within Slopsmith: `lib/psarc.py::unpack_psarc` for PSARC TOC filenames, `lib/patcher.py::unpack_psarc` (a duplicate of the above in the patcher flow), and `lib/sloppak.py::_unpack_zip` using `ZipFile.extractall()` without a member filter. These extractors concatenate archive-entry filenames directly onto the extraction root without validation, allowing attackers to supply filenames containing `..` segments, absolute paths, or backslash separators. This enables path-traversal attacks, potentially leading to arbitrary file writes outside the extraction directory. In the default Docker configuration (running as root), this vulnerability can escalate to arbitrary remote code execution on the host.

Defensive priority

High priority due to potential for remote code execution in default Docker configurations.

Recommended defensive actions

• Update Slopsmith to version 0.2.9-alpha.5 or later
• Limit exposure of Slopsmith instances to the public internet
• Exercise caution when handling PSARC or sloppak archives from untrusted sources
• Pull the latest Docker image once it's available
• Review and validate archive filenames before extraction

Evidence notes

The primary evidence for this vulnerability comes from the Slopsmith GitHub repository and the NVD CVE record. The vulnerability affects Slopsmith versions prior to 0.2.9-alpha.5. Defenders should verify the patched version and review archive extraction processes to ensure proper validation of filenames.

Official resources