CVSS 4.0
5.4 mediumCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCVE-2025-71463 Scapy before 2.7.0 Insecure Deserialization RCE via Session Files
Medium (5.4) in secdev scapy. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
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__().
Severity
CVSS 3.1
6.7 mediumCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-502 Deserialization of Untrusted Data
- OWASP Top 10
- A08:2025 Software or Data Integrity Failures
- Published
- Modified
- Assigned by
- VulnCheck (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2025-71463 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-71463?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-71463?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-71463 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2025-71463)
HTML:
<a href="https://cve.bz/cve/CVE-2025-71463"><img src="https://cve.bz/cve/badge/CVE-2025-71463.svg" alt="CVE-2025-71463"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| secdev scapy | before 2.7.0 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS and 4 more | scapy | no fix listed | UBUNTU-CVE-2025-71463 |
From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.
Attack patterns (CAPEC)
- CAPEC-586 Object Injection Likelihood: Medium · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.