# CVE-2024-25176: Memory corruption in n/a

> A stack-buffer-overflow in LuaJIT allows attackers to execute arbitrary code or cause denial of service via crafted numeric formatting.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jul 2025
- **Updated:** 3 Nov 2025
- **Also known as:** ALPINE-CVE-2024-25176, AZL-65370, AZL-65394, AZL-65427, BELL-CVE-2024-25176, DEBIAN-CVE-2024-25176, ECHO-0c63-8fb4-89c9, GHSA-xvfg-m24j-r4pm, MINI-rmq7-986g-jrjf, UBUNTU-CVE-2024-25176

## What is CVE-2024-25176?

CVE-2024-25176 is a critical memory corruption vulnerability in n/a, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240626 have a stack-buffer-overflow in lj_strfmt_wfnum in lj_strfmt_num.c.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2024-25176?

It affects 1 product.


Products: Luajit Luajit.

## How do I fix CVE-2024-25176?

Upgrade to a fixed version.

## Is CVE-2024-25176 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25176 exists.

## Other vulnerabilities in n/a

- [CVE-2024-25178](https://insights.sbomify.com/CVE-2024-25178/): Memory corruption in n/a (critical 9.1)
- [CVE-2019-19391](https://insights.sbomify.com/CVE-2019-19391/): Memory corruption in n/a (critical 9.1)
- [CVE-2024-25177](https://insights.sbomify.com/CVE-2024-25177/): Null dereference in n/a (high 7.5)
- [CVE-2020-24372](https://insights.sbomify.com/CVE-2020-24372/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25176 and fix it if it is affected.

What it is: CVE-2024-25176 is a critical memory corruption vulnerability in n/a, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25176 exists.

Affected product: n/a. 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-2024-25176/ (Markdown: https://insights.sbomify.com/CVE-2024-25176/index.md)
```

## Sources

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

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