CVE-2025-30402 is a high-severity (CVSS 8.1) remote code execution vulnerability in org.pytorch:executorch-android. A fix is available for org.pytorch:executorch-android — see the affected versions and patch details below.
ExecuTorch vulnerable to Heap-based Buffer Overflow attack
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-30402.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.pytorch:executorch-android🐍executorch📦github.com/pytorch/executorchReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, PyPI, SwiftURL packages — download data is not available via public APIs for these ecosystems.
Description
A heap-buffer-overflow vulnerability in the loading of ExecuTorch methods can cause the runtime to crash and potentially result in code execution or other undesirable effects. This issue affects ExecuTorch prior to commit 93b1a0c15f7eda49b2bc46b5b4c49557b4e9810f
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.pytorch:executorch-android | all versions | 0.7.0-rc1org.pytorch:executorch-android:0.7.0-rc1 |
| 🐍PyPI | executorch | all versions | 0.7.0pip install --upgrade 'executorch==0.7.0' |
| 📦SwiftURL | github.com/pytorch/executorch | all versions | 0.7.0-rc1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.pytorch:executorch-android, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.pytorch:executorch-android to 0.7.0-rc1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-30402 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Frequently Asked Questions
Is CVE-2025-30402 in your dependencies?
Find it across Maven, PyPI, SwiftURL, including transitive dependencies.