# CVE-2025-54952: ExecuTorch integer overflow vulnerability leads to code execution

> Integer overflow in ExecuTorch model loading allows attackers to trigger code execution via crafted models.

- **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:** No
- **Published:** 7 Aug 2025
- **Updated:** 8 Aug 2025
- **Also known as:** GHSA-33r8-vrx9-rmcv, PYSEC-2026-1351

## What is CVE-2025-54952?

CVE-2025-54952 is a critical vulnerability in Meta Platforms, Inc ExecuTorch, published on 7 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An integer overflow vulnerability in the loading of ExecuTorch models can cause smaller-than-expected memory regions to be allocated, potentially resulting in code execution or other undesirable effects. This issue affects ExecuTorch prior to commit 8f062d3f661e20bb19b24b767b9a9a46e8359f2b.

Weakness: CWE-680 (Integer Overflow to Buffer Overflow)

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

3 open source packages ship an affected version, including executorch.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `executorch` | PyPI | All versions to 0.6.0 | None |
| `executorch` | PyPI | All versions to 0.6.0 | None |
| `executorch` | PyPI | All versions to 0.6.0 | None |

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

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

## Is CVE-2025-54952 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54952 is a critical vulnerability in Meta Platforms, Inc ExecuTorch, published on 7 Aug 2025. 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-54952 in the wild and no public exploit code.

Affected packages and fixed versions:
- executorch (PyPI): affected all versions up to 0.6.0; no fix listed
- executorch (PyPI): affected all versions up to 0.6.0; no fix listed
- executorch (PyPI): affected all versions up to 0.6.0; no fix listed

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-54952/ (Markdown: https://insights.sbomify.com/CVE-2025-54952/index.md)
```

## Sources

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

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