Is torch affected by CVE-2025-63396?

PyPI torch is affected in <=2.5.0-NA, <=2.7.1-NA.

Is CVE-2025-63396 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.1%.

low

CVE-2025-63396

Q: Is CVE-2025-63396 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.1%.

PyPI · torch

Summary

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).

Severity: low
EPSS: 0.1% (p2)
Also known as: BIT-pytorch-2025-63396, PYSEC-2025-210
Published: 2025-11-12

References

Related advisories

CVE-2025-32434 — critical · PyPI/torch
CVE-2026-4538 — high · PyPI/torch
CVE-2025-55560 — high · PyPI/torch
CVE-2025-55558 — high · PyPI/torch
CVE-2025-55557 — high · PyPI/torch
CVE-2025-55553 — high · PyPI/torch
CVE-2025-55552 — high · PyPI/torch
CVE-2025-55551 — high · PyPI/torch

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.