| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in PyTorch 2.7.0 and classified as problematic. The affected element is the function torch.cummin. Performing a manipulation results in denial of service.
This vulnerability is identified as CVE-2025-55557. There is not any exploit available.
Details
A vulnerability classified as problematic has been found in PyTorch 2.7.0. This affects the function torch.cummin. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:
A Name Error occurs in pytorch v2.7.0 when a PyTorch model consists of torch.cummin and is compiled by Inductor, leading to a Denial of Service (DoS).
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-55557 since 08/13/2025. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 266120 (Linux Distros Unpatched Vulnerability : CVE-2025-55557), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Tenable (266120) and CERT Bund (WID-SEC-2025-2139). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Open Source PyTorch
Product
Name
Version
Website
- Product: https://github.com/pytorch/pytorch/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 266120
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-55557
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/13/2025 CVE reserved09/25/2025 Advisory disclosed
09/25/2025 VulDB entry created
10/03/2025 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CVE: CVE-2025-55557 (🔒)
GCVE (CVE): GCVE-0-2025-55557
GCVE (VulDB): GCVE-100-325881
CERT Bund: WID-SEC-2025-2139 - PyTorch: Mehrere Schwachstellen
Entry
Created: 09/25/2025 17:57Updated: 10/03/2025 23:35
Changes: 09/25/2025 17:57 (52), 09/27/2025 06:14 (7), 09/30/2025 05:32 (2), 10/03/2025 23:35 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.