LiveActive security incident?Get immediate response
CVE Record

CVE-2025-63396: An issue was discovered in PyTorch v2.5 and v2.7.1.

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

LowCVSS 3.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity denial-of-service issue in PyTorch profiling. If profiling is used and profiler.stop() is omitted, PyTorch can crash or hang while finalizing the PythonTracer, disrupting the local job or process.

Executive priority

Treat as routine maintenance unless critical ML workflows rely on PyTorch profiling. The business risk is localized job disruption, not data theft or remote compromise.

Technical view

CVE-2025-63396 affects PyTorch v2.5 and v2.7.1. The reported condition is tied to torch.profiler.profile PythonTracer finalization when profiler.stop() is not called. CVSS 3.1 is 3.3 with local attack vector, low complexity, low privileges, no confidentiality or integrity impact, and low availability impact.

Likely exposure

Exposure is most likely in development, ML training, testing, or observability workflows that use torch.profiler.profile on PyTorch v2.5 or v2.7.1.

Exploitation context

The CVE is not listed as KEV, and the supplied sources do not claim active exploitation. The issue requires local, low-privileged access and appears limited to causing a crash or hang.

Researcher notes

Evidence is narrow: the bundle names affected PyTorch versions and the profiler.stop() omission condition, but does not provide a patch version. Validate behavior only in controlled environments and avoid publishing weaponized reproductions.

Mitigation direction

  • Inventory PyTorch deployments and identify v2.5 or v2.7.1 use.
  • Ensure profiler-using code explicitly calls profiler.stop().
  • Avoid running profiling paths in production jobs unless required.
  • Monitor the PyTorch issue for vendor-confirmed fixes or workarounds.
  • Apply vendor guidance when a fixed release is identified.

Validation and detection

  • Search code for torch.profiler.profile usage.
  • Confirm profiling code calls profiler.stop() on all paths.
  • Review ML jobs for hangs or crashes during profiler finalization.
  • Check dependency manifests for PyTorch v2.5 or v2.7.1.
  • Track the referenced PyTorch issue for resolution status.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-667: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-63396 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.3CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L1.81.4CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

3.3Low
CVSS 3.1 vector shape for CVE-2025-63396Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-667

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.