CVE-2025-46149

In PyTorch before 2.7.0, when inductor is used, nn.Fold has an assertion error.

Published: 2025-09-25 Last update: 2025-10-03 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-46149 is rated Low Risk (30.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.33%). 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-2025-46149

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.02% 0.33% +0.31%
2 2026-02-21 0.06% 0.02% -0.04%
3 2026-01-25 — 0.06% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-46149

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-46149

OS Trackers for CVE-2025-46149

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

Affected software / configurations for CVE-2025-46149

Vendor Product Version Raw CPE
linuxfoundation pytorch >= 2.6.0, < 2.7.0 cpe:2.3:a:linuxfoundation:pytorch:*:*:*:*:*:python:*:*

References for CVE-2025-46149

cvelogic Threat Intelligence