← Back
CVE-2025-30402
Vulnerability in executorch (CVE-2025-30402)
Summary
vulnerability in executorch (CVE-2025-30402). Confidential information can be exposed externally. Mitigation: upgrade to `0.7.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-30402** has been found in executorch.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade executorch to **0.7.0** or later.
If unsure, ask your IT team or search "executorch CVE-2025-30402" on the vendor's site.
CVE-2025-30402 (executorch) — CWE-122 /
Attack vector: remote (network-reachable) / unauthenticated
Patched: `0.7.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-122) exists in executorch.
📍 Affected scope
executorch — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **0.7.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'executorch' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'executorch' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `executorch` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade executorch to 0.7.0ステージング環境で 0.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
executorch
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.7.0"}]}]
maven
org.pytorch:executorch-android
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.7.0-rc1"}]}]
swift
github.com/pytorch/executorch
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.7.0-rc1"}]}]
PyPI
executorch
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.7.0"}]}]
SwiftURL
github.com/pytorch/executorch
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.7.0-rc1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-30402
- advisory https://github.com/advisories/GHSA-h952-963h-rv99
- package https://github.com/pytorch/executorch
- package https://pypi.org/project/executorch
- web https://github.com/pytorch/executorch/commit/93b1a0c15f7eda49b2bc46b5b4c49557b4e9810f
- web https://www.facebook.com/security/advisories/cve-2025-30402