CVE-2025-54065VulnerabilityPublished 3 Dec 2025

CVE-2025-54065: ZDoom gzdoom · Improper Control of Dynamically-Managed Code Resources

Affects ZDoom gzdoomSource CVE Database V5

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.8High

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 3 Dec 2025
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 2026-10-25.

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 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

Affected software

Product	Affected	Fixed in
GitHubzdoom/gzdoom`pkg:github/zdoom/gzdoom`Other threats	Affected <=4.14.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Restrict execution of untrusted or user-generated ZScript code within GZDoom environments, limiting script permissions and sandboxing script execution where possible. 2. Monitor and audit script activities for unusual behavior, such as attempts to manipulate FState or VMFunction structures or unexpected memory access patterns. 3. Educate users and developers about the risks of running unverified scripts and enforce strict code review policies for custom mods or scripts. 4. Isolate GZDoom instances in virtualized or containerized environments to limit the impact of potential exploitation on host systems. 5. Implement host-based intrusion detection systems (HIDS) that can detect anomalous JIT code modifications or control flow redirections. 6. Prepare for rapid deployment of official patches once released by the vendor; track vendor communications closely. 7. Limit local user privileges to the minimum necessary to reduce the risk of exploitation from low-privilege accounts. 8. Consider network segmentation to prevent lateral movement if a compromise occurs. 9. Regularly update all related software components and dependencies to reduce the attack surface. 10. Engage with the GZDoom community and security forums to stay informed about emerging threats and mitigation techniques.

Description

GZDoom is a feature centric port for all Doom engine games. GZDoom is an open source Doom engine. In versions 4.14.2 and earlier, ZScript actor state handling allows scripts to read arbitrary addresses, write constants into the JIT-compiled code section, and redirect control flow through crafted FState and VMFunction structures. A script can copy FState structures into a writable buffer, modify function pointers and state transitions, and cause execution of attacker-controlled bytecode, leading to arbitrary code execution.

Impact

For European organizations, the impact of CVE-2025-54065 can be significant, especially those involved in gaming, software development, or digital entertainment sectors where GZDoom is used. Successful exploitation allows attackers to execute arbitrary code, potentially leading to unauthorized access to sensitive data, manipulation of game logic or software behavior, and compromise of the host system’s integrity. Although the vulnerability requires local access and user interaction, it could be exploited in multi-user environments or through social engineering to run malicious scripts. This could lead to lateral movement within networks or serve as a foothold for further attacks. Confidentiality is highly impacted as arbitrary memory reads are possible, and integrity is compromised due to arbitrary code execution. Availability is not directly affected. The lack of known exploits in the wild provides a window for organizations to implement mitigations before active exploitation occurs. However, the presence of JIT code manipulation increases the risk of sophisticated attacks that evade traditional detection methods. Organizations relying on GZDoom for development or entertainment should consider the risk of insider threats or compromised user accounts that could trigger exploitation.

CWE-913Improper Control of Dynamically-Managed Code Resources (opens in a new tab)
Class weaknessOWASP Top 10 A01:2021: Broken Access Control (opens in a new tab)
The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.
Implementation · Input Validation
For any externally-influenced input, check the input against an allowlist of acceptable values.
Implementation · Architecture and Design · Refactoring
Refactor the code so that it does not need to be dynamically managed.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/ZDoom/gzdoom/security/advisories/GHSA-prhc-chfw-32jg (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Dec 2025, 18:33 UTC

WeaknessesCWE-913

Technical details

References

Community reviews

Related threats