Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
A local desktop app that must extract an attacker-supplied archive implies AV:L and UI:R; the traversal is an arbitrary file-write primitive so I:H with C:N/A:N.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
Doom Launcher 3.8.1.0 is vulnerable to Directory Traversal due to missing file path validation during the extraction of game files
AnalysisAI
Directory traversal (path/Zip-Slip style) in Doom Launcher 3.8.1.0 lets a maliciously crafted game-file archive write files outside the intended extraction directory because file paths are not validated during extraction. Any user who imports a booby-trapped WAD/game package into the launcher can have arbitrary files created or overwritten on their system, potentially leading to code execution. There is no public exploit identified at time of analysis, KEV status is not listed, and EPSS is very low at 0.07% (21st percentile).
Technical ContextAI
Doom Launcher is a Windows front-end/manager for launching and organizing classic Doom (id Software) games, mods, and WAD/PK3 archives. The flaw is a classic CWE-22 Improper Limitation of a Pathname to a Restricted Directory: when the launcher unpacks a game-file archive it uses attacker-controlled entry names verbatim, so path components such as '../' or absolute paths escape the target folder. This is the well-known 'Zip Slip' pattern, where an extraction routine trusts archive metadata instead of canonicalizing and confining each output path beneath the intended destination.
RemediationAI
No vendor-released patched version is identified in the available data, so a specific upgrade target cannot be cited; monitor the project issue at https://github.com/nstlaurent/DoomLauncher/issues/369 and the advisory at https://jeroscope.com/advisories/2025/jero-2025-014/ for a fixed release and upgrade as soon as one is published. Until then, the practical compensating control is operational: do not import or extract game-file archives (WAD/PK3/zip packages) from untrusted or unverified sources, since exploitation depends on processing attacker-supplied content - the trade-off is losing the convenience of one-click community mod imports. Where feasible, run Doom Launcher under a low-privileged, sandboxed, or containerized user account so that any out-of-bounds writes are confined and cannot reach sensitive system or startup locations, accepting some loss of integration with the host filesystem.
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2025-208755