CVE-2025-3730: PyTorch LossCTC.cpp torch.nn.functional.ctc_loss denial of service
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: azl3 pytorch 2.2.2-6 on Azure Linux 3.0 2.2.2-6; azl3 pytorch 2.2.2-7 on Azure Linux 3.0 2.2.2-6; cbl2 pytorch 2.0.0-8 on CBL Mariner 2.0 2.0.0-8.
Low priority for now. Upgrade to azl3 pytorch 2.2.2-6 on Azure Linux 3.0 2.2.2-6; azl3 pytorch 2.2.2-7 on Azure Linux 3.0 2.2.2-6; cbl2 pytorch 2.0.0-8 on CBL Mariner 2.0 2.0.0-8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 16, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 27th percentile
- CWE
- CWE-404
Report tools
Action score
19
Low priority for now.
- CVSS
- 19 / 40 · 4.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulDB
- 4.8
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linuxfoundation | pytorch | cpe:2.3:a:linuxfoundation:pytorch |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulDB). Independent of NVD's CPE analysis and usually ahead of it.
n/a PyTorch
- 2.6.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linuxfoundation pytorch2.6.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | pytorch | from 0 | — |
| Debian:14 | pytorch | before 2.12.0+dfsg2-1 | 2.12.0+dfsg2-1 |
| PyPI | torch | before 2.8.0 | 2.8.0 |
Same product
linuxfoundation: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-48063In PyTorch <=2.4.1, the RemoteModule has Deserialization RCE.39Monitor
- CVE-2022-45907In PyTorch before trunk/89695, torch.jit.annotations.parse_type_line can cause arbitrary code execution because eval is used unsafely.39Monitor
- CVE-2025-32434PyTorch: `torch.load` with `weights_only=True` leads to remote code execution38Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-3121Apr 2, 2025 · PyTorch torch.jit.jit_module_from_flatbuffer memory corruption19Monitor
- ← EarlierCVE-2025-3136Apr 3, 2025 · PyTorch CUDACachingAllocator.cpp torch.cuda.memory.caching_allocator_delete memory corruption19Monitor
- Later →CVE-2025-46148Sep 25, 2025 · In PyTorch through 2.6.0, when eager is used, nn.PairwiseDistance(p=2) produces incorrect results.21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 pytorch 2.2.2-6 on Azure Linux 3.0 | 2.2.2-6 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 pytorch 2.2.2-7 on Azure Linux 3.0 | 2.2.2-6 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 pytorch 2.0.0-8 on CBL Mariner 2.0 | 2.0.0-8 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 pytorch 2.0.0-9 on CBL Mariner 2.0 | 2.0.0-8 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 pytorch 2.0.0-9 on CBL-Mariner 2.0 | 2.0.0-8 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:pytorch | 2.12.0+dfsg2-1 · Debian:14 | Package registry (OSV) |
| PyPI:torch | 2.8.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Default436352 (VulDB User)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-295317 days apartPyTorch torch.mkldnn_max_pool2d denial of service19Monitor
Not on record for this CVE: EPSS history · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-404 · Improper Resource Shutdown or ReleaseCVSS vector
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-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.