Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious Lua mod/scenario
-
DeliveryDistribute via Workshop or file share
-
ExploitVictim loads content in-game
-
Executionloadstring triggers Lua type confusion
-
ImpactCorrupt memory for client-side code execution
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Type safety enforcement
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a victim running Civilization V 1.0.3.144 to load attacker-supplied Lua content (a mod, map, or scenario) that reaches the loadstring function in the game's Lua Sandbox, triggering the type confusion - this is the user interaction captured by UI:P and described as a 'three-click' flow. No authentication or special privileges are needed (PR:N). The decisive limiting factor is that the malicious content must be actively loaded by the user; there is no automatic or server-side trigger, so exploitation is targeted and social-engineering-dependent rather than unattended. No vendor-confirmed fixed version or official mitigation is available, as the vendor did not respond. |
| Impact | The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P, VC:L/VI:L/VA:L, E:P) yields a medium 5.3 and signals remote delivery with no privileges but with required user interaction and only Low impact to each of confidentiality, integrity and availability. This conflicts sharply with the researcher write-up, whose title ('three-click RCE in Civ V') and PoC repository name claim full remote code execution - the CVE Description itself establishes only a type confusion (CWE-843) in the Lua Sandbox loadstring function, so the true impact is unresolved and should be verified before trusting either extreme. There is no CISA KEV listing and no EPSS score in the supplied data, so widespread or automated exploitation is not evidenced; the E:P (Proof-of-Concept) maturity and the this_month vuln.today decision label both point to a real-but-not-emergency priority. The hard limiter is UI: exploitation needs a victim to load attacker-supplied Lua content, which rules out unattended mass exploitation and makes this a targeted, social-engineering-dependent client-side issue rather than a server-side wormable flaw. Net: patch/mitigate on a normal (this-month) cadence, but resolve the impact discrepancy (Low vs. claimed RCE) with an independent look at the PoC rather than accepting the RCE claim as confirmed. |
| Exploit ScenarioDerived | An attacker crafts a malicious Civilization V mod, map, or scenario containing Lua that abuses the loadstring function in the game's Lua Sandbox, then distributes it (e.g. via Steam Workshop or a shared file); when a victim loads it in version 1.0.3.144 the type confusion is triggered, causing memory corruption and, per the researcher, client-side code execution. A public PoC reference exists (a GitHub exploit.lua and a blog write-up); it is not verified as working exploit code. The 'three-click' interaction and required loading of untrusted content mean exploitation depends on user action, not automation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
A type-confusion flaw in the Lua Sandbox of Civilization V 1.0.3.144 (function loadstring) lets remote attackers deliver crafted Lua content - a mod, map or scenario - that, once loaded by the victim, corrupts memory and can compromise confidentiality, integrity and availability of the game process. No authentication or privileges are required (CVSS 4.0 vector is PR:N), but the user must actively load the malicious content, which the independent assessment describes as a 'three-click' interaction flow; the reported CVSS 4.0 severity is 5.3 (medium) with Low impacts to each of C/I/A, while the independent CVSS 3.1 assessment rates all three as High. A public PoC reference exists (a VulDB entry and a blog plus GitHub exploit.lua linked from the advisory); it is not verified as working exploit code, and no CISA KEV listing or confirmed active exploitation is present in the supplied data. The vendor was contacted and did not respond, so no fixed version or official mitigation is available.
RemediationAI
No vendor-released patch identified at time of analysis: 2K Games was contacted about the disclosure and did not respond, so there is no fixed version to upgrade to and no official mitigation from the vendor. Until one appears, the only effective control is to prevent hostile Lua content from reaching loadstring - do not load mods, maps or scenarios from untrusted sources, audit existing subscriptions and downloaded Workshop content, and treat any shared .lua-driven content as potentially executable code rather than data; the trade-off is loss of community-mod functionality for that install. Run the game as a non-privileged local user and, where practical, inside a restricted or disposable environment (VM, separate OS account) so that memory corruption in the game process does not translate into access to the user's documents and credentials; the trade-off is reduced performance or additional setup overhead. Network filtering alone is not a reliable mitigation because the payload is user-loaded content rather than an inbound service request. Monitor https://vuldb.com/vuln/426179 and https://drbloop.dev/blog/three-click-rce-in-civi-v for a vendor response or a published fix version, and re-test any build that ships an updated Lua Sandbox.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Civilization V embeds a Lua scripting engine that runs community mods, maps and scenarios, and the affected component is its Lua Sandbox - the isolation layer intended to constrain what such scripts can do. CWE-843 (Type Confusion) means the game's loadstring handling can be made to treat one object as a different, incompatible type, which in a native-backed interpreter typically yields memory corruption and unpredictable read/write behaviour rather than a clean scripting-layer error; the supplied tags classify the consequences as memory corruption and information disclosure. The CPE wildcard cpe:2.3:a:2k_games:civilization_v:*:*:*:*:*:*:*:* lists all versions of the product, while the disclosure names 1.0.3.144 specifically; the exact mechanism by which loadstring is reached, the precise malformed construct that triggers the confusion, and whether exploitation reliably escapes the sandbox to native code execution are not described in the available sources - the referenced researcher blog is titled as a 'three-click RCE', but that claim is not independently verified here. Delivery is remote in the sense that the malicious Lua content can be distributed over a network (AV:N in both the CVSS 4.0 input vector and the assessed CVSS 3.1 vector), but execution only occurs after the target user loads that content inside the game.
Know when Civilization V gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Victim must load attacker-supplied Lua content (UI:R), no auth (PR:N); researcher PoC indicates client code execution (C/I/A:H), though the description confirms only type confusion.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A vulnerability was determined in 2K Games Civilization V 1.0.3.144. Impacted is the function loadstring of the component Lua Sandbox. Executing a manipulation can lead to type confusion. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-109603
GHSA-qqv4-567f-4g4p
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB