# CVE-2025-63396: Denial of service in n/a

> Attackers can cause a Denial of Service in PyTorch by omitting profiler.stop(), leading to crashes or hangs during finalization.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Nov 2025
- **Updated:** 5 Jul 2026
- **Also known as:** BIT-pytorch-2025-63396, DEBIAN-CVE-2025-63396, ECHO-00c5-1dba-56e8, GHSA-3w6q-rqw9-h6qx, PYSEC-2025-210, UBUNTU-CVE-2025-63396

## What is CVE-2025-63396?

CVE-2025-63396 is a low-severity denial of service vulnerability in n/a, published on 12 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in PyTorch v2.5 and v2.7.1. Omission of profiler.stop() can cause torch.profiler.profile (PythonTracer) to crash or hang during finalization, leading to a Denial of Service (DoS).

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2025-63396?

2 open source packages ship an affected version, including pytorch and torch. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pytorch` | Bitnami | From 2.5.0 | 2.5.1, 2.8.0 |
| `torch` | PyPI | All versions to 2.5.0-NA | None |

Products: Linuxfoundation Pytorch.

## How do I fix CVE-2025-63396?

Upgrade pytorch to a fixed version for your release line: 2.5.1 or 2.8.0.

## Is CVE-2025-63396 being exploited?

There is no known exploitation of CVE-2025-63396 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-48063](https://insights.sbomify.com/CVE-2024-48063/): Deserialization in n/a (critical 9.8)
- [CVE-2022-45907](https://insights.sbomify.com/CVE-2022-45907/): PyTorch vulnerable to arbitrary code execution (critical 9.8)
- [CVE-2025-32434](https://insights.sbomify.com/CVE-2025-32434/): PyTorch: `torch.load` with `weights_only=True` leads to remote code execution (critical 9.3)
- [CVE-2026-24747](https://insights.sbomify.com/CVE-2026-24747/): PyTorch Vulnerable to Remote Code Execution via Untrusted Checkpoint Files (high 8.8)
- [CVE-2024-31583](https://insights.sbomify.com/CVE-2024-31583/): Pytorch use-after-free vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63396 and fix it if it is affected.

What it is: CVE-2025-63396 is a low-severity denial of service vulnerability in n/a, published on 12 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-63396 in the wild and no public exploit code.

Affected packages and fixed versions:
- pytorch (Bitnami): affected from 2.5.0; fixed in 2.5.1, 2.8.0
- torch (PyPI): affected all versions up to 2.5.0-NA; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-63396/ (Markdown: https://insights.sbomify.com/CVE-2025-63396/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63396
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63396
- OSV: https://osv.dev/vulnerability/CVE-2025-63396

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-63396/
Summaries are generated and may contain mistakes; the official description above is the record.