# CVE-2025-67482: Lua segfault in unpack()

> A null pointer dereference in the Lua unpack function allows attackers to cause a denial of service in Wikimedia Scribunto and luasandbox.

- **Severity:** Low 1.7 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Feb 2026
- **Updated:** 2 Mar 2026
- **Also known as:** DEBIAN-CVE-2025-67482, GHSA-xf8x-crg7-q946, UBUNTU-CVE-2025-67482

## What is CVE-2025-67482?

CVE-2025-67482 is a low-severity vulnerability in Wikimedia Foundation Scribunto, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in Wikimedia Foundation Scribunto, Wikimedia Foundation luasandbox. This vulnerability is associated with program files includes/Engines/LuaCommon/lualib/mwInit.Lua, library.C.

This issue affects Scribunto: from * before 1.39.16, 1.43.6, 1.44.3, 1.45.1; luasandbox: from * before fea2304f8f6ab30314369a612f4f5b165e68e95a.

## Which versions are affected by CVE-2025-67482?


## How do I fix CVE-2025-67482?

Upgrade to a fixed version.

## Is CVE-2025-67482 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67482 and fix it if it is affected.

What it is: CVE-2025-67482 is a low-severity vulnerability in Wikimedia Foundation Scribunto, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67482 in the wild and no public exploit code.

Affected product: Wikimedia Foundation Scribunto. 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-2025-67482/ (Markdown: https://insights.sbomify.com/CVE-2025-67482/index.md)
```

## Sources

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

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