How severe is GHSA-46h3-79wf-xr6c?

No CVSS score has been assigned to GHSA-46h3-79wf-xr6c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-46h3-79wf-xr6c?

GHSA-46h3-79wf-xr6c affects the following packages: picklescan (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-46h3-79wf-xr6c?

Update picklescan to 0.0.34 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-46h3-79wf-xr6c is resolved across your whole dependency graph.

How do I detect GHSA-46h3-79wf-xr6c in my PyPI dependencies?

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

How do I mitigate GHSA-46h3-79wf-xr6c 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-46h3-79wf-xr6c?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-46h3-79wf-xr6c can be triaged on real exposure rather than presence alone.

Is GHSA-46h3-79wf-xr6c actively exploited in the wild?

No public exploit code has been indexed for GHSA-46h3-79wf-xr6c 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.

What is the EPSS score for GHSA-46h3-79wf-xr6c?

GHSA-46h3-79wf-xr6c has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-46h3-79wf-xr6c?

GHSA-46h3-79wf-xr6c is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-46h3-79wf-xr6c published, and has it been updated?

GHSA-46h3-79wf-xr6c was published on December 30, 2025 and was last updated on July 8, 2026. 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-46h3-79wf-xr6c — picklescan

Fix: mmaitre314/picklescan@f2dea43

GHSA-46h3-79wf-xr6c is a Deserialization of Untrusted Data vulnerability in picklescan. A fix is available for picklescan — see the affected versions and patch details below.

Picklescan is vulnerable to RCE via missing detection when calling built-in python _operator.attrgetter

Also known asCVE-2025-71367

Published

Dec 30, 2025

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-46h3-79wf-xr6c.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

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

Picklescan uses _operator.attrgetter, which is a built-in python library function to execute remote pickle files.

Details

The attack payload executes in the following steps:

First, the attacker crafts the payload by calling the _operator.attrgetter function in the reduce method.
Then, when the victim, after checking whether the pickle file is safe by using the Picklescan library and finding that this library doesn't detect any dangerous functions, decides to call pickle.load() on this malicious pickle file, it leads to remote code execution.

PoC

import pickle
import pickletools
opcode3 = b'''cbuiltins
__import__
(Vos
tRp0
0c_operator
attrgetter
(Vsystem
tR(g0
tR(Vecho "pwned by _operator.attrgetter"
tR.'''
pickletools.dis(opcode3)
pickle.loads(opcode3)

This PoC can't be easily create by pickle.dumps, so it was manually built.

Impact

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

Report by

Pinji Chen ([email protected]) from the NISL lab (https://netsec.ccert.edu.cn/about) at Tsinghua University, Guanheng Liu ([email protected]).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`picklescan`	all versions	0.0.34`pip install --upgrade 'picklescan==0.0.34'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for picklescan, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update picklescan to 0.0.34 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-46h3-79wf-xr6c 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-46h3-79wf-xr6c can be triaged on real exposure rather than presence alone.

Tailored to GHSA-46h3-79wf-xr6c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Picklescan uses _operator.attrgetter, which is a built-in python library function to execute remote pickle files. ### Details The attack payload executes in the following steps: - First, the attacker crafts the payload by calling the _operator.attrgetter function in the reduce method. - Then, when the victim, after checking whether the pickle file is safe by using the Picklescan library and finding that this library doesn't detect any dangerous functions, decides to call pickle.load() on this malicious pickle file, it leads to remote code execution. ### PoC ``` import pickle imp

O3 Security · Impact-Aware SCA

Is GHSA-46h3-79wf-xr6c in your dependencies?

O3 Security finds GHSA-46h3-79wf-xr6c 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