CVE-2025-30405
CRITICALCVE-2025-30405 is a critical-severity (CVSS 9.8) CWE-190 vulnerability in org.pytorch:executorch-android. O3 Security confirms whether CVE-2025-30405 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
ExecuTorch integer overflow vulnerability
Blast Radius
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
An integer overflow vulnerability in the loading of ExecuTorch models can cause objects to be placed outside their allocated memory area, potentially resulting in code execution or other undesirable effects. This issue affects ExecuTorch prior to commit 0830af8207240df8d7f35b984cdf8bc35d74fa73.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.pytorch:executorch-android | all versions | 0.7.0 |
| 🐍PyPI | executorch | all versions | 0.7.0 |
| 📦SwiftURL | github.com/pytorch/executorch | all versions | 0.7.0 |
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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.pytorch:executorch-android to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-30405 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-30405 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-30405. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-30405 in your dependencies?
O3 detects CVE-2025-30405 across Maven, PyPI, SwiftURL dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.