{"answers":{"affected":"2 open source packages ship an affected version, including pytorch and torch. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-63396 in the wild and no public exploit code.","fix":"Upgrade pytorch to a fixed version for your release line: 2.5.1 or 2.8.0.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-63396 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-63396 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pytorch (Bitnami): affected from 2.5.0; fixed in 2.5.1, 2.8.0\n- torch (PyPI): affected all versions up to 2.5.0-NA; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-63396/ (Markdown: https://insights.sbomify.com/CVE-2025-63396/index.md)","id":"CVE-2025-63396","markdown":"https://insights.sbomify.com/CVE-2025-63396/index.md","name":"CVE-2025-63396","record":{"aliases":["BIT-pytorch-2025-63396","DEBIAN-CVE-2025-63396","ECHO-00c5-1dba-56e8","GHSA-3w6q-rqw9-h6qx","PYSEC-2025-210","UBUNTU-CVE-2025-63396"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PyTorch machine learning library","requires_auth":"low_privilege","summary":"Attackers can cause a Denial of Service in PyTorch by omitting profiler.stop(), leading to crashes or hangs during finalization.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pytorch","vendor":"linuxfoundation"}],"cvss":{"score":3.3,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-667","name":"Improper Locking"}],"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).","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Denial of service in n/a","id":"CVE-2025-63396","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-63397"},"packages":[{"ecosystem":"Bitnami","fixed":["2.5.1","2.8.0"],"introduced":["2.5.0","2.7.1"],"last_affected":[],"package":"pytorch","purl":"pkg:bitnami/pytorch","source":"BIT-pytorch-2025-63396"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.5.0-NA","2.7.1-NA"],"package":"torch","purl":"pkg:pypi/torch","source":"PYSEC-2025-210"}],"prev":{"headline":"DO NOT USE THIS CVE RECORD.","id":"CVE-2025-63391"},"products":["n/a"],"published":"2025-11-12","related":[{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2024-48063","kev_date_added":null,"published":"2024-10-29"},{"cvss_score":9.8,"headline":"PyTorch vulnerable to arbitrary code execution","id":"CVE-2022-45907","kev_date_added":null,"published":"2022-11-26"},{"cvss_score":9.3,"headline":"PyTorch: `torch.load` with `weights_only=True` leads to remote code execution","id":"CVE-2025-32434","kev_date_added":null,"published":"2025-04-18"},{"cvss_score":8.8,"headline":"PyTorch Vulnerable to Remote Code Execution via Untrusted Checkpoint Files","id":"CVE-2026-24747","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":7.8,"headline":"Pytorch use-after-free vulnerability","id":"CVE-2024-31583","kev_date_added":null,"published":"2024-04-17"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-55551","kev_date_added":null,"published":"2025-09-25"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-55553","kev_date_added":null,"published":"2025-09-25"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can cause a Denial of Service in PyTorch by omitting profiler.stop(), leading to crashes or hangs during finalization.","url":"https://insights.sbomify.com/CVE-2025-63396/"}