CVE-2025-3730 json
PyTorch LossCTC.cpp torch.nn.functional.ctc_loss denial of service
published last yr. modified last mo. also BIT-pytorch-2025-3730 , EUVD-2025-11538 , GHSA-887c-mr87-cxwp , PYSEC-2026-1970
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
A vulnerability, which was classified as problematic, was found in PyTorch 2.6.0. Affected is the function torch.nn.functional.ctc_loss of the file aten/src/ATen/native/LossCTC.cpp. The manipulation leads to denial of service. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The name of the patch is 46fc5d8e360127361211cb237d5f9eef0223e567. It is recommended to apply a patch to fix this issue. The security policy of the project warns to use unknown models which might establish malicious effects.
Patch / fix
- pypi torch 2.8.0
- bitnami pytorch 2.7.0
- pytorch Debian 14 2.12.0+dfsg2-1
debian advisories DEBIAN-CVE-2025-3730
- pytorch Azure Linux 3.0 2.2.2-6
- pytorch CBL-Mariner 2.0 2.0.0-8
azure linux advisories AZL-60500AZL-60577
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- github.com/timocafe/tewart-pytorch@46fc5d8 commit
- github.com/pytorch/pytorch@01f226b commit
- github.com/pytorch/pytorch#150981 pull request
Is CVE-2025-3730 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-3730 updated cvss 3.3
PyTorch: PyTorch LossCTC.cpp torch.nn.functional.ctc_loss denial of service
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/pytorch/pytorch/issues/150835 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/pytorch/pytorch/issues/150835#issue-2979082232 referenced PoC, tagged "exploit" by a source, unverified
- vuldb.com https://vuldb.com/?submit.553645 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| CNA | 3.0 | 3.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| CNA | 2.0 | 1.7 | AV:L/AC:L/Au:S/C:N/I:N/A:P |
| GitHub | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | torch | <2.8.0 |
2.8.0 |
| bitnami | pytorch | >=2.6.0, <2.7.0 |
2.7.0 |
Affected products
- n/a PyTorch
Classification
- Weakness
-
- CWE-404 Improper Resource Shutdown or Release
References
-
github.com
/pytorch/pytorch/pull/150981
issue-tracking, web, patch
-
github.com
/timocafe/tewart-pytorch/commit/46fc5d8e360127361211cb237d5f9eef0223e567
patch, web
-
github.com
/pytorch/pytorch/commit/01f226bfb8f2c343f5c614a6bbf685d91160f3af
web
-
github.com
/pytorch/pytorch/issues/150835
issue-tracking, exploit, web, vendor-advisory, advisory
-
github.com
/pytorch/pytorch/issues/150835#issue-2979082232
exploit, issue-tracking, vendor-advisory, advisory
-
vuldb.com
/?submit.553645
third-party-advisory, web, exploit, vdb-entry, advisory
-
vuldb.com
/?id.305076
vdb-entry, technical-description, web, third-party-advisory, advisory
-
vuldb.com
/?ctiid.305076
signature, permissions-required, web, vdb-entry, report
-
nvd.nist.gov
/vuln/detail/CVE-2025-3730
advisory, web
-
github.com
/pytorch/pytorch
package
-
pypi.org
/project/torch
package
-
github.com
/advisories/GHSA-887c-mr87-cxwp
advisory
Sources
- CVE List CVE-2025-3730
- GitHub Advisory GHSA-887c-mr87-cxwp
- NVD CVE-2025-3730
- OSV BIT-pytorch-2025-3730
- OSV PYSEC-2026-1970
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.