# CVE-2025-2149: PyTorch Quantized Sigmoid Module nnq_Sigmoid initialization

> Improper initialization in PyTorch's quantized sigmoid module allows local attackers to manipulate scale and zero-point arguments, potentially causing unexpected behavior.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Mar 2025
- **Updated:** 10 Mar 2025
- **Also known as:** BIT-pytorch-2025-2149, DEBIAN-CVE-2025-2149, ECHO-a0c5-9cb9-6a53, GHSA-x3gm-94wq-g975, PYSEC-2025-190, UBUNTU-CVE-2025-2149

## What is CVE-2025-2149?

CVE-2025-2149 is a low-severity vulnerability in PyTorch, published on 10 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in PyTorch 2.6.0+cu124. It has been rated as problematic. Affected by this issue is the function nnq_Sigmoid of the component Quantized Sigmoid Module. The manipulation of the argument scale/zero_point leads to improper initialization. The attack needs to be approached locally. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used.

Weakness: CWE-665 (Improper Initialization)

## Which versions are affected by CVE-2025-2149?

4 open source packages ship an affected version, including pytorch and torch. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pytorch` | Bitnami | From 2.6.0 | 2.7.0 |
| `torch` | PyPI | All versions to 2.6.0 | None |
| `torch` | PyPI | All versions to 2.6.0 | None |
| `torch` | PyPI | All versions to 2.6.0-cu124 | None |

Products: Linuxfoundation Pytorch.

## How do I fix CVE-2025-2149?

Upgrade pytorch to 2.7.0 or later.

## Is CVE-2025-2149 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2149 exists.

## Other vulnerabilities in PyTorch

- [CVE-2024-48063](https://insights.sbomify.com/CVE-2024-48063/): Deserialization in n/a (critical 9.8)
- [CVE-2022-45907](https://insights.sbomify.com/CVE-2022-45907/): PyTorch vulnerable to arbitrary code execution (critical 9.8)
- [CVE-2025-32434](https://insights.sbomify.com/CVE-2025-32434/): PyTorch: `torch.load` with `weights_only=True` leads to remote code execution (critical 9.3)
- [CVE-2026-24747](https://insights.sbomify.com/CVE-2026-24747/): PyTorch Vulnerable to Remote Code Execution via Untrusted Checkpoint Files (high 8.8)
- [CVE-2024-31583](https://insights.sbomify.com/CVE-2024-31583/): Pytorch use-after-free vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2149 and fix it if it is affected.

What it is: CVE-2025-2149 is a low-severity vulnerability in PyTorch, published on 10 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2149 exists.

Affected packages and fixed versions:
- pytorch (Bitnami): affected from 2.6.0; fixed in 2.7.0
- torch (PyPI): affected all versions up to 2.6.0; no fix listed
- torch (PyPI): affected all versions up to 2.6.0; no fix listed
- torch (PyPI): affected all versions up to 2.6.0-cu124; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2149/ (Markdown: https://insights.sbomify.com/CVE-2025-2149/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2149
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2149
- OSV: https://osv.dev/vulnerability/CVE-2025-2149

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2149/
Summaries are generated and may contain mistakes; the official description above is the record.