Skip to main content
VulnerabilityPublished

CVE-2025-63396: PyTorch · CWE-667

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-63396· Low 3.3

Not known to be exploited · CVSS 3.3 Low.

Data as of 13 Nov 2026, 18:30 UTC

CVSS 3.1 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.13.3
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
PyPItorchpkg:pypi/torchOther threatsAffected
  • =2.5
  • =2.7.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should ensure that profiler.stop() is properly called to avoid triggering this issue. Monitor vendor advisories for any forthcoming patches or updates addressing this vulnerability.

Description

A denial of service vulnerability exists in PyTorch versions 2.5 and 2.7.1 where omitting the call to profiler.stop() can cause the torch.profiler.profile (PythonTracer) to crash or hang during finalization.

References

Community reviews

Loading reviews…