CVE-2024-31583

Pytorch before version v2.2.0 was discovered to contain a use-after-free vulnerability in torch/csrc/jit/mobile/interpreter.cpp.

Published: 2024-04-17 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-31583 is rated Low Risk (37.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.27%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-31583

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.05% 0.27% +0.22%
2 2025-12-14 0.06% 0.05% -0.01%
3 2025-09-06 — 0.06% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-31583

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-31583

GitHub Security Advisory for CVE-2024-31583

GHSA-pg7h-5qx3-wjr3 · Severity: high · Ecosystem: pip — Pytorch use-after-free vulnerability

OS Trackers for CVE-2024-31583

vendor priority summary link
debian not yet assigned CVE-2024-31583 not yet assigned priority: Debian including 1 source packages (pytorch), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2024-31583
ubuntu medium CVE-2024-31583 medium priority: Ubuntu including 1 source packages (pytorch), 8 status rows across 8 suites (focal, jammy, mantic, noble, oracular, plucky, questing, upstream): ignored 3, needs-triage 3, DNE 2. https://ubuntu.com/security/CVE-2024-31583

Affected software / configurations for CVE-2024-31583

Vendor Product Version Raw CPE
linuxfoundation pytorch < 2.2.0 cpe:2.3:a:linuxfoundation:pytorch:*:*:*:*:*:python:*:*

References for CVE-2024-31583

cvelogic Threat Intelligence