Quick answers
- Is CVE-2025-54952 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-54952 being exploited in the wild.
- How severe is CVE-2025-54952?
- Medium severity, with a CVSS score of 4, published 7 July 2026.
- Which products and versions are affected?
- executorch (PyPI) ECOSYSTEM:introduced=0,last_affected=0.6.0.
- Is there a fix for CVE-2025-54952?
- A patch was published on 2025-08-08: Fix available in commit 8f062d3f661e20bb19b24b767b9a9a46e8359f2b Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-54952 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2025-54952?
- Check whether you run executorch (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An integer overflow vulnerability exists in the memory allocation logic of ExecuTorch's model loader (runtime/core/memory_allocator.h). When loading a model file, insufficient bounds checking on size calculations causes a smaller-than-expected memory region to be allocated. The vulnerability is triggered when processing a crafted ExecuTorch model, and requires user interaction (loading a malicious model file). A successful exploit can result in heap buffer overflow, leading to code execution or information disclosure. The fix is available in commit 8f062d3f661e20bb19b24b767b9a9a46e8359f2b (adding overflow checks in the allocation logic).
Affected products
- Meta ExecuTorch prior to commit 8f062d3f661e20bb19b24b767b9a9a46e8359f2b (versions 0.1.0 through 0.6.0 affected)
Identifiers
- CVE-2025-54952
- GHSA-33r8-vrx9-rmcv
- PYSEC-2026-1351
Timeline
- 2025-08-08: disclosed
- 2025-08-08: patched: Fix available in commit 8f062d3f661e20bb19b24b767b9a9a46e8359f2b