PyTorch: Manipulation of the argument scale/zero_point leads to improper initialization via Quantized Sigmoid Module

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2025-2149: 0.26% estimated exploitation activity in the next 30 days; percentile 17.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability was found in PyTorch 2.6.0+cu124. It has been rated as problematic. Affected by this issue is the function nnqSigmoid of the component Quantized Sigmoid Module. The manipulation of the argument scale/zeropoint 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.

Published by the source

10 Mar 2025, 15:30 UTC

Last modified by the source

9 Jun 2026, 22:11 UTC

Source last checked

26 Oct 2026, 13:45 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-x3gm-94wq-g975

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-x3gm-94wq-g975

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-2149

Advisory: PyTorch: Manipulation of the argument scale/zero_point leads to improper initialization via Quantized Sigmoid Module
IDs: CVE-2025-2149, GHSA-x3gm-94wq-g975
Record: https://patchnext.com/advisories/cve-2025-2149 (revision 3, source checked 26 Oct 2026, 13:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI torch: affected <= 2.6.0

## Suggested inspection (read-only)
- `python -m pip show torch`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on torch.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-x3gm-94wq-g975 (OSV record GHSA-x3gm-94wq-g975 lists affected ranges: PyPI torch >=0 <=2.6.0)
- Verified: https://github.com/advisories/GHSA-x3gm-94wq-g975 (GitHub-reviewed advisory GHSA-x3gm-94wq-g975 lists affected ranges: PyPI torch >=0 <=2.6.0)

Commands are suggestions: review each one before running it.