VulnerabilityPublished 16 Mar 2026Updated 17 Mar 2026

CVE-2025-66687: Doom Launcher · CVE-2025-66687 is a high-severity directory traversal

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2025-66687, organizations should implement the following specific measures: 1) Restrict file extraction paths by enforcing strict validation and sanitization of file names and paths before extraction, ensuring no directory traversal sequences are allowed. 2) Use application-level whitelisting to restrict which files and directories the Doom Launcher can access or modify. 3) Monitor file system changes in directories used by the launcher to detect suspicious activity or unauthorized file writes. 4) Isolate the launcher execution environment using sandboxing or containerization to limit the impact of potential exploitation. 5) Until an official patch is released, consider disabling automatic extraction features or using alternative tools for game file management. 6) Educate users and administrators about the risks of opening untrusted game files and encourage verification of file sources. 7) Regularly check for updates from the vendor and apply patches promptly once available. These targeted actions go beyond generic advice by focusing on controlling file path handling and limiting the attack surface specific to the launcher’s extraction process.

Description

CVE-2025-66687 is a high-severity directory traversal vulnerability in Doom Launcher version 3.8.1.0. The flaw arises from inadequate validation of file paths during the extraction of game files, allowing attackers to write files outside the intended directory. This vulnerability can be exploited remotely without authentication or user interaction, potentially leading to unauthorized disclosure of sensitive files. Although no known exploits are currently in the wild, the vulnerability poses a significant risk due to its ease of exploitation and high impact on confidentiality. Organizations using Doom Launcher for game management should prioritize patching or applying mitigations once available. The threat primarily affects users in countries with large gaming communities and significant usage of Doom Launcher. Immediate mitigation steps include restricting file extraction paths, employing application whitelisting, and monitoring file system changes.

Impact

The primary impact of CVE-2025-66687 is unauthorized disclosure of sensitive information due to directory traversal during file extraction. Attackers can exploit this vulnerability to write files outside the intended directory, potentially exposing configuration files, credentials, or other sensitive data stored on the system. This can lead to further compromise if attackers gain access to critical files or use the vulnerability as a foothold for additional attacks. Although the vulnerability does not directly affect system integrity or availability, the confidentiality breach can have severe consequences, especially in environments where sensitive user data or proprietary information is stored. Organizations relying on Doom Launcher for game deployment or management may face data leakage risks, reputational damage, and potential compliance violations. The ease of exploitation without authentication or user interaction increases the threat level, making automated attacks feasible. The absence of known exploits in the wild currently limits immediate widespread impact, but the vulnerability remains a significant risk until patched.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Mar 2026, 01:04 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats