Bug 2433612 (CVE-2026-24747)

Summary:	CVE-2026-24747 pytorch: PyTorch: Arbitrary code execution via malicious checkpoint file loading
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	jkoehler, lphiri, lx
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in PyTorch, a Python package for tensor computation. A remote attacker could craft a malicious checkpoint file, which, when loaded using the `weights_only` unpickler, could lead to memory corruption. This vulnerability may enable an attacker to achieve arbitrary code execution on the affected system.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2433773, 2463454, 2433774, 2433775, 2433776, 2433777, 2433778, 2433779, 2433780
Bug Blocks:

Description OSIDB Bzimport 2026-01-27 22:02:17 UTC

PyTorch is a Python package that provides tensor computation. Prior to version 2.10.0, a vulnerability in PyTorch's `weights_only` unpickler allows an attacker to craft a malicious checkpoint file (`.pth`) that, when loaded with `torch.load(..., weights_only=True)`, can corrupt memory and potentially lead to arbitrary code execution. Version 2.10.0 fixes the issue.

Comment 2 Alexander Lent 2026-01-30 05:36:47 UTC

The CVE listing seems to have a patch attached, but I honestly can't tell if it fixes the CVE or not; it seems unrelated.

Comment 3 Alexander Lent 2026-02-16 04:35:57 UTC

This is sadly distinct from CVE-2025-32434. Moreover, any vulns in weights_only=True are real security issues for our users - it's supposed to be a safe function.

Comment 4 Alexander Lent 2026-02-16 04:36:55 UTC

This appears to hit F42 and F43 and F44 despite the RH bug filing. Delightful. :/

Unfortunately, both the commit and bug number provided in the NVD for this vuln seem unrelated.

Luckily, I was able to find the patch:
https://github.com/pytorch/pytorch/commit/0e2459f08fc5329979e6ad986014278f2a87618c