CVE-2025-2999 json
PyTorch torch.nn.utils.rnn.unpack_sequence memory corruption
published last yr. modified 2mo ago also BIT-pytorch-2025-2999 , EUVD-2025-8755 , GHSA-vgrw-7cvw-pwgx , PYSEC-2025-193
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
A vulnerability was found in PyTorch 2.6.0. It has been rated as critical. Affected by this issue is the function torch.nn.utils.rnn.unpack_sequence. The manipulation leads to memory corruption. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used.
Patch / fix
- pypi torch 2.9.1
- bitnami pytorch 2.7.0
- pytorch Debian 14 2.12.0+dfsg2-1
debian advisories DEBIAN-CVE-2025-2999
Is CVE-2025-2999 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/pytorch/pytorch/issues/149622#issue-2935495265 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:L/VI:L/VA:L/SC:N/SI:N/SA:N |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 3.0 | 5.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 2.0 | 4.3 | AV:L/AC:L/Au:S/C:P/I:P/A:P |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | torch | <2.9.1 <=2.6.0-NA |
2.9.1 |
| bitnami | pytorch | >=2.6.0, <2.7.0 |
2.7.0 |
Affected products
- n/a PyTorch
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
github.com
/pytorch/pytorch/commit/494518046816d29099b7d056a74ffa5c244fdcdd
web
-
github.com
/pytorch/pytorch/issues/149622#issue-2935495265
exploit, issue-tracking, web, vendor-advisory, advisory, report
-
github.com
/pytorch/pytorch/issues/149622
issue-tracking, web, vendor-advisory, advisory, report
-
vuldb.com
/?id.302048
vdb-entry, technical-description, web, third-party-advisory, advisory
-
vuldb.com
/?ctiid.302048
signature, permissions-required, web, vdb-entry, report
-
vuldb.com
/?submit.524198
third-party-advisory, web, vdb-entry, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-2999
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/torch/PYSEC-2025-193.yaml
web
-
github.com
/pytorch/pytorch
package
-
github.com
/advisories/GHSA-vgrw-7cvw-pwgx
advisory
Sources
- CVE List CVE-2025-2999
- GitHub Advisory GHSA-vgrw-7cvw-pwgx
- NVD CVE-2025-2999
- OSV BIT-pytorch-2025-2999
- OSV PYSEC-2025-193
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.