← Back
UBUNTU-CVE-2026-24747
Vulnerability in pytorch (UBUNTU-CVE-2026-24747)
Summary
vulnerability in pytorch (UBUNTU-CVE-2026-24747). Successful exploitation can lead to full system takeover. Exploitable via ``weights_only``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2026-24747** has been found in pytorch.
Attackers can target a specific entry point like ``weights_only`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "pytorch UBUNTU-CVE-2026-24747" on the vendor's site.
UBUNTU-CVE-2026-24747 (pytorch) —
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `weights_only`
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** (unclassified) exists in pytorch. Attackers reach the vulnerable code path via ``weights_only`` without authentication.
📍 Affected scope
pytorch — . Attack surface: `weights_only`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 'pytorch' .` 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 'pytorch' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pytorch` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:22.04:LTS
pytorch
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:25.10
pytorch
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:26.04:LTS
pytorch
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- report https://ubuntu.com/security/CVE-2026-24747
- report https://www.cve.org/CVERecord?id=CVE-2026-24747
- report https://github.com/pytorch/pytorch/163122/commit/954dc5183ee9205cbe79876ad05dd2d9ae752139
- report https://github.com/pytorch/pytorch/issues/163105
- report https://github.com/pytorch/pytorch/releases/tag/v2.10.0
- report https://github.com/pytorch/pytorch/security/advisories/GHSA-63cw-57p8-fm3p