PytorchApplication · Linuxfoundation
CVE-2025-3001
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability classified as critical was found in PyTorch 2.6.0. This vulnerability affects the function torch.lstm_cell. The manipulation leads to memory corruption. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA memory corruption vulnerability exists in PyTorch 2.6.0's torch.lstm_cell function. The vulnerability has a local attack vector and publicly available exploit code, with a CVSS score of 5.3 indicating moderate severity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
PytorchApplication
= 2.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed PyTorch versionRun 'python -c "import torch; print(torch.__version__)"' to retrieve the installed PyTorch version numberAffected if The version shown is exactly 2.6.0
-
Locate torch.lstm_cell usage in codeSearch Python source files, notebooks, and scripts for imports of torch.nn.LSTMCell or calls to torch.lstm_cell, or search for the string 'lstm_cell' using grep/grep -rAffected if Code explicitly invokes torch.lstm_cell or torch.nn.LSTMCell in any application running on the affected PyTorch version
-
Check for dynamic usage in runtimeInspect running Python processes or imported modules in memory using 'python -c "import torch; print(hasattr(torch, 'lstm_cell'))"' to confirm the function exists in the installed buildAffected if The function is present and accessible in the PyTorch 2.6.0 installation
-
Assess local access contextReview user permissions and access controls on the system where PyTorch runs; determine if untrusted users have local access to execute Python code or load malicious modelsAffected if The system running PyTorch 2.6.0 permits local access by users who could invoke the vulnerable function
You are affected if PyTorch version 2.6.0 is installed AND the torch.lstm_cell function is accessible in your environment where local users can trigger it.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied patches for PyTorch 2.6.0 when available; if immediate patching is not feasible, consider restricting access to the affected torch.lstm_cell function and monitoring for indicators of exploitation.
Fix this in Pytorch
Scoped from the published advisory
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3001 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data