# CVE-2025-46417: Picklescan Vulnerable to Exfiltration via DNS via linecache and ssl.get_server_certificate

> Attackers can exfiltrate data via DNS after deserialization because the scanner's unsafe globals list omits ssl functions.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Apr 2025
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-93mv-x874-956g, PYSEC-2025-34

## What is CVE-2025-46417?

CVE-2025-46417 is a medium-severity unsafe deserialization vulnerability in Picklescan, published on 24 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The unsafe globals in Picklescan before 0.0.25 do not include ssl. Consequently, ssl.get_server_certificate can exfiltrate data via DNS after deserialization.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2025-46417?

3 open source packages ship an affected version, including picklescan. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `picklescan` | PyPI | All versions | 0.0.25 |
| `picklescan` | PyPI | All versions | 0.0.25 |
| `picklescan` | PyPI | All versions | 0.0.25 |

Products: Mmaitre314 Picklescan.

## How do I fix CVE-2025-46417?

Upgrade picklescan to 0.0.25 or later.

## Is CVE-2025-46417 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46417 exists.

## Other vulnerabilities in Picklescan

- [CVE-2025-10155](https://insights.sbomify.com/CVE-2025-10155/): PickleScan Security Bypass Using Misleading File Extension (critical 9.3)
- [CVE-2025-10156](https://insights.sbomify.com/CVE-2025-10156/): PickleScan Security Bypass via Bad CRC in ZIP Archive (critical 9.3)
- [CVE-2025-10157](https://insights.sbomify.com/CVE-2025-10157/): PickleScan Bypasses Unsafe Globals Check Using Submodule Imports (critical 9.3)
- [CVE-2025-71348](https://insights.sbomify.com/CVE-2025-71348/): picklescan - Arbitrary Code Execution via torch.utils._config_module.load_config Bypass (high 7.6)
- [CVE-2025-71357](https://insights.sbomify.com/CVE-2025-71357/): picklescan - Arbitrary Code Execution via Undetected idlelib.pyshell.ModifiedInterpreter.runcommand (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46417 and fix it if it is affected.

What it is: CVE-2025-46417 is a medium-severity unsafe deserialization vulnerability in Picklescan, published on 24 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46417 exists.

Affected packages and fixed versions:
- picklescan (PyPI): affected all versions; fixed in 0.0.25
- picklescan (PyPI): affected all versions; fixed in 0.0.25
- picklescan (PyPI): affected all versions; fixed in 0.0.25

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/CVE-2025-46417/ (Markdown: https://insights.sbomify.com/CVE-2025-46417/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-46417
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-46417
- OSV: https://osv.dev/vulnerability/CVE-2025-46417

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-46417/
Summaries are generated and may contain mistakes; the official description above is the record.