# CVE-2026-116370: 2K Games Sid Meier's Civilization VI Lua sandbox loadstring type confusion


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-x6v8-mwjf-8mrc

## What is CVE-2026-116370?

CVE-2026-116370 is a medium-severity vulnerability in 2K Games Sid Meier's Civilization VI, published on 26 Oct 2026. 

### Official description

A security flaw has been discovered in 2K Games Sid Meier's Civilization VI 1.0.12.68. The affected element is the function loadstring of the component Lua sandbox. Performing a manipulation results in type confusion. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2026-116370?

It affects 1 product.


Products: 2k Sid Meiers Civilization Vi.

## How do I fix CVE-2026-116370?

No fix has been published for CVE-2026-116370 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116370 being exploited?

There is no known exploitation of CVE-2026-116370 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-116370 (github_poc): https://github.com/drbloop2000/Sid-Meier-s-Civilization-VI-RCE

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116370 and fix it if it is affected.

What it is: CVE-2026-116370 is a medium-severity vulnerability in 2K Games Sid Meier's Civilization VI, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116370 in the wild and no public exploit code.

Affected product: 2K Games Sid Meier's Civilization VI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116370/ (Markdown: https://insights.sbomify.com/CVE-2026-116370/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116370
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116370
- OSV: https://osv.dev/vulnerability/CVE-2026-116370

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116370/
Summaries are generated and may contain mistakes; the official description above is the record.