# CVE-2025-71463: Scapy before 2.7.0 Insecure Deserialization RCE via Session Files

> Attackers who trick users into loading a malicious pickle session file can execute arbitrary Python code via Scapy's session loading.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`load_session`)
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** DEBIAN-CVE-2025-71463, GHSA-cq46-m9x9-j8w2, GHSA-f572-w3j5-2qmc, UBUNTU-CVE-2025-71463

## What is CVE-2025-71463?

CVE-2025-71463 is a medium-severity unsafe deserialization vulnerability in secdev scapy, published on 13 Nov 2026. 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

Scapy before 2.7.0 contains an insecure deserialization vulnerability in the load_session function that allows attackers to execute code by supplying a malicious pickle session file. Attackers can trick users into loading a crafted .pkl.gz file via the -s option or conf.session, executing embedded Python code through __reduce__().

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

1 open source package ship an affected version, including scapy.

An affected version is only exploitable if your software calls load_session. Many projects that include it are not exposed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `scapy` | PyPI | `pkg:pypi/scapy` | All versions to 2.6.1 | None |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | affected | `scapy` |  |

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

Upgrade to a fixed version.

## Is CVE-2025-71463 being exploited?

There is no known exploitation of CVE-2025-71463 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-71463 is a medium-severity unsafe deserialization vulnerability in secdev scapy, published on 13 Nov 2026. 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: There is no known exploitation of CVE-2025-71463 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls load_session. Many projects that include it are not exposed.

Affected packages and fixed versions:
- scapy (PyPI): affected all versions up to 2.6.1; 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.
   If an affected version is present, also search the code for calls to load_session and report whether any exist.
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-71463/ (Markdown: https://insights.sbomify.com/CVE-2025-71463/index.md)
```

## Sources

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

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