cve.bz

CVE-2025-32434 linuxfoundation pytorch: Deserialization of Untrusted Data

9.3 criticalEPSS 2.4%Fix available

Critical (9.3) in linuxfoundation pytorch. EPSS 2.4% estimated probability of exploitation activity in the next 30 days. Fixed in torch 2.6.0.

On this page
PyTorch is a Python package that provides tensor computation with strong GPU acceleration and deep neural networks built on a tape-based autograd system. In version 2.5.1 and prior, a Remote Command Execution (RCE) vulnerability exists in PyTorch when loading a model using torch.load with weights_only=True. This issue has been patched in version 2.6.0.

Severity

CVSS 4.0

9.3 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
2.4% (unchanged from 2.4% a week ago; 2.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 84th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2025-04-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-32434 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-32434?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-32434?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-32434 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
linuxfoundation:pytorchbefore 2.6.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-53q9-r3pm-6pq6PyPItorch<2.6.02.6.0
PYSEC-2025-41PyPItorch<2.6.02.6.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11pytorch1.7.1-7+deb11u1DLA-4389-1
Debian12pytorchno fix listedDEBIAN-CVE-2025-32434
Debian13, 14pytorch2.6.0+dfsg-1DEBIAN-CVE-2025-32434
Azure Linux2pytorch2.0.0-8AZL-60880
Azure Linux3pytorch2.2.2-6AZL-60877

From the distributions' data via OSV.dev: the Debian Security Tracker; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON