Epic Games vulnerabilities
Published CVEs affecting Epic Games products: 4 record(s), with severity, exploitation and fixes.
CVE-2026-14765
High · 7.7
CWE-1188 Oct 14, 2026
Epic Games Unreal Engine Insecure Default URL Scheme Allowance in LaunchURL
Epic Games Unreal Engine versions up to and including 5.8.0 ship with an insecure default configuration for the LaunchURL Blueprint node (UKismetSystemLibrary::LaunchURL). The URL scheme filter (FURLRequestFilter) is empty by default, which permits all URL schemes. On Windows, this results in a call to ShellExecuteW() with the open verb, so a supplied file:/// URI causes the referenced file to be executed. Any Unreal Engine game that loads user-generated content containing Blueprints is vulnerable to command execution via a malicious local file or a remote file on a WebDAV share. This is an instance of CWE-1188 (Initialization of a Resource with an Insecure Default).
CVE-2025-61973
High · 8.8
CWE-284 Jan 15, 2026
Improper Access Control in Epic Games Epic Games Store
A local privilege escalation vulnerability exists during the installation of Epic Games Store via the Microsoft Store. A low-privilege user can replace a DLL file during the installation process, which may result in unintended elevation of privileges.
CVE-2021-47742
High · 8.8
CWE-732 Dec 31, 2025
Epic Games Psyonix Rocket League <=1.95 Elevation of Privileges via Insecure Permissions
Epic Games Psyonix Rocket League <=1.95 contains an insecure permissions vulnerability that allows authenticated users to modify executable files with full access permissions. Attackers can leverage the 'F' (Full) flag for the 'Authenticated Users' group to change executable files and potentially escalate system privileges.
CVE-2021-47739
High · 8.4
CWE-428 Dec 23, 2025
Epic Games Easy Anti-Cheat 4.0 Local Privilege Escalation via Unquoted Service Path
Epic Games Easy Anti-Cheat 4.0 contains an unquoted service path vulnerability that allows local non-privileged users to execute arbitrary code with elevated system privileges. Attackers can exploit the service configuration by inserting malicious code in the system root path that would execute with LocalSystem privileges during application startup.