# GHSA-m9mp-6x32-5rhg: scio is vunerable to Remote Command Execution through PyTorch

> Attackers can execute arbitrary code via malicious PyTorch models in scio, requiring users to upgrade dependencies.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Oct 2025

## What is GHSA-m9mp-6x32-5rhg?

GHSA-m9mp-6x32-5rhg is an unsafe deserialization vulnerability in scio-pypi, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

### Impact
PyTorch reported a [**critical** vulnerability](https://github.com/pytorch/pytorch/security/advisories/GHSA-53q9-r3pm-6pq6) when using `torch.load`, even with option `weights_only=True`, for `torch <= 2.5.1`.

In `scio <= 1.0.0`, the lower bound for `torch` is `2.3`.

### Patches
The lower bound was changed to `torch >= 2.6`, starting from `scio >= 1.0.1` (currently in dev state).

### Workarounds
You can manually check that you are using `torch >= 2.6`.

## Which versions are affected by GHSA-m9mp-6x32-5rhg?

2 open source packages ship an affected version, including scio-pypi.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `scio-pypi` | PyPI | All versions to 1.0.0 | None |
| `scio-pypi` | PyPI | All versions to 1.0.0 | None |

## How do I fix GHSA-m9mp-6x32-5rhg?

No fix has been published for GHSA-m9mp-6x32-5rhg yet. Limit exposure of the affected software until one is available.

## Is GHSA-m9mp-6x32-5rhg being exploited?

There is no known exploitation of GHSA-m9mp-6x32-5rhg in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-m9mp-6x32-5rhg and fix it if it is affected.

What it is: GHSA-m9mp-6x32-5rhg is an unsafe deserialization vulnerability in scio-pypi, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-m9mp-6x32-5rhg in the wild and no public exploit code.

Affected packages and fixed versions:
- scio-pypi (PyPI): affected all versions up to 1.0.0; no fix listed
- scio-pypi (PyPI): affected all versions up to 1.0.0; 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/GHSA-m9mp-6x32-5rhg/ (Markdown: https://insights.sbomify.com/GHSA-m9mp-6x32-5rhg/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-m9mp-6x32-5rhg

---
From sbomify Insights: https://insights.sbomify.com/GHSA-m9mp-6x32-5rhg/
Summaries are generated and may contain mistakes; the official description above is the record.