CVE-2025-63396

LOWNVD 3.33.3—Trending — 3 sources updated this week

3.3

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

CVSS v3: 3.3
EG Score: 3.3(medium)
EPSS: 9.0%
KEV: Not listed

Published

November 12, 2025

Last Modified

January 2, 2026

References (4)

cve@mitrehttp://pytorch.com
cve@mitrehttps://github.com/Daisy2ang
cve@mitrehttps://github.com/pytorch/pytorch
cve@mitrehttps://github.com/pytorch/pytorch/issues/156563

Affected Packages

(1 across 1 ecosystem)

PyPI(1)

Package	Vulnerable range	Fixed in	Dependents
torch	—	—	—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-667

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:13 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 19:21 UTCEG score recompute
2026-05-29 19:21 UTCGHSA enrichment
2026-05-29 13:44 UTCepss_batch

Frequently asked(5)

What is CVE-2025-63396?

CVE-2025-63396 is a low vulnerability published on November 12, 2025. 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).

When was CVE-2025-63396 disclosed?

CVE-2025-63396 was first published in the National Vulnerability Database on November 12, 2025, with the most recent update on January 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2025-63396 actively exploited?

CVE-2025-63396 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2025-63396?

CVE-2025-63396 has a CVSS v3 base score of 3.3 (NVD).

How do I remediate CVE-2025-63396?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-63396, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-63396

Explore →

Is Your Infrastructure Affected by CVE-2025-63396?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2025-63396

📅 Published

🔄 Last Modified

🔗 References (4)

Affected Packages

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2025-63396?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)