How severe is GHSA-vr7h-p6mm-wpmh?

No CVSS score has been assigned to GHSA-vr7h-p6mm-wpmh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vr7h-p6mm-wpmh?

GHSA-vr7h-p6mm-wpmh affects the following packages: picklescan (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-vr7h-p6mm-wpmh?

Update picklescan to 0.0.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vr7h-p6mm-wpmh is resolved across your whole dependency graph.

How do I detect GHSA-vr7h-p6mm-wpmh in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for picklescan. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-vr7h-p6mm-wpmh 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-vr7h-p6mm-wpmh?

O3 pinpoints whether GHSA-vr7h-p6mm-wpmh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-vr7h-p6mm-wpmh actively exploited in the wild?

No public exploit code has been indexed for GHSA-vr7h-p6mm-wpmh 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-vr7h-p6mm-wpmh published, and has it been updated?

GHSA-vr7h-p6mm-wpmh was published on August 22, 2025 and was last updated on August 22, 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

GHSA-vr7h-p6mm-wpmh

Picklescan missing detection when calling pytorch function torch.jit.unsupported_tensor_ops.execWrapper

Published

Aug 22, 2025

Updated

Aug 22, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐍picklescan

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

Summary

Using torch.jit.unsupported_tensor_ops.execWrapper function, which is a pytorch library function to execute remote pickle file.

Details

The attack payload executes in the following steps:

First, the attacker craft the payload by calling to torch.jit.unsupported_tensor_ops.execWrapper function in reduce method Then when the victim after checking whether the pickle file is safe by using Picklescan library and this library doesn't dectect any dangerous functions, decide to pickle.load() this malicious pickle file, thus lead to remote code execution.

PoC


import torch.jit.unsupported_tensor_ops as unsupported_tensor_ops

class EvilTorchJitUnsupportedTensorOpsExecWrapper:
    def __reduce__(self):
        code = '__import__("os").system("whoami")'
        glob = {}
        loc = {}
        return unsupported_tensor_ops.execWrapper, (code, glob, loc)

Impact

Who is impacted? Any organization or individual relying on picklescan to detect malicious pickle files inside PyTorch models. What is the impact? Attackers can embed malicious code in pickle file that remains undetected but executes when the pickle file is loaded. Supply Chain Attack: Attackers can distribute infected pickle files across ML models, APIs, or saved Python objects.

Corresponding

https://github.com/FredericDT https://github.com/Qhaoduoyu

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`picklescan`	all versions	0.0.28

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for picklescan. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update picklescan to 0.0.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vr7h-p6mm-wpmh is resolved across your whole dependency graph.
Workarounds
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 pinpoints whether GHSA-vr7h-p6mm-wpmh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vr7h-p6mm-wpmh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Using torch.jit.unsupported_tensor_ops.execWrapper function, which is a pytorch library function to execute remote pickle file. ### Details The attack payload executes in the following steps: First, the attacker craft the payload by calling to torch.jit.unsupported_tensor_ops.execWrapper function in reduce method Then when the victim after checking whether the pickle file is safe by using Picklescan library and this library doesn't dectect any dangerous functions, decide to pickle.load() this malicious pickle file, thus lead to remote code execution. ### PoC ``` import torch

O3 Security · Impact-Aware SCA

Is GHSA-vr7h-p6mm-wpmh in your dependencies?

O3 detects GHSA-vr7h-p6mm-wpmh across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works