How severe is GHSA-m9mp-6x32-5rhg?

No CVSS score has been assigned to GHSA-m9mp-6x32-5rhg yet. Review the advisory details and affected package list to assess your exposure.

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

GHSA-m9mp-6x32-5rhg affects the following packages: scio-pypi (PyPI). Ecosystems affected: PyPI.

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

No patched version of scio-pypi has shipped for GHSA-m9mp-6x32-5rhg yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-m9mp-6x32-5rhg in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for scio-pypi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-m9mp-6x32-5rhg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-m9mp-6x32-5rhg?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m9mp-6x32-5rhg can be triaged on real exposure rather than presence alone.

Is GHSA-m9mp-6x32-5rhg actively exploited in the wild?

No public exploit code has been indexed for GHSA-m9mp-6x32-5rhg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-m9mp-6x32-5rhg published, and has it been updated?

GHSA-m9mp-6x32-5rhg was published on October 9, 2025 and was last updated on October 9, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-m9mp-6x32-5rhg — scio-pypi

GHSA-m9mp-6x32-5rhg is a security vulnerability in scio-pypi. No vendor fix is recorded yet; mitigation options are listed below.

scio is vunerable to Remote Command Execution through PyTorch

Published

Oct 9, 2025

Updated

Oct 9, 2025

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Oct 9, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍scio-pypi

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

PyTorch reported a critical vulnerability 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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`scio-pypi`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for scio-pypi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of scio-pypi has shipped for GHSA-m9mp-6x32-5rhg yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m9mp-6x32-5rhg can be triaged on real exposure rather than presence alone.

Tailored to GHSA-m9mp-6x32-5rhg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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`.

O3 Security · Impact-Aware SCA

Is GHSA-m9mp-6x32-5rhg in your dependencies?

O3 Security finds GHSA-m9mp-6x32-5rhg across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works