CVE-2026-24747
Linuxfoundation Pytorch insecure deserialization
- Published27 Jan 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:24977
- https://access.redhat.com/security/cve/CVE-2026-24747
- https://bugzilla.redhat.com/show_bug.cgi?id=2433612
- https://github.com/pytorch/pytorch/163122/commit/954dc5183ee9205cbe79876ad05dd2d9ae752139
- https://github.com/pytorch/pytorch/issues/163105
- https://github.com/pytorch/pytorch/releases/tag/v2.10.0
- https://github.com/pytorch/pytorch/security/advisories/GHSA-63cw-57p8-fm3p
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-24747.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-24747 being actively exploited?
CVE-2026-24747 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.81%.
How severe is CVE-2026-24747?
CVE-2026-24747 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.81% probability of exploitation.
Which products are affected by CVE-2026-24747?
Affected products include Linuxfoundation Pytorch.
How do I fix CVE-2026-24747?
Upgrade affected software to a fixed version, for example Linuxfoundation Pytorch 2.10.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-24747 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.