CVE-2025-71463 in Scapyinfo

Summary

by MITRE • 11/13/2026

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__().

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/13/2026

The Scapy network packet sniffer and generator utility contains a critical insecure deserialization vulnerability in versions prior to 2.7.0 that poses significant risks to system integrity when handling session data files. This flaw resides specifically within the load_session function, which is designed to restore previously saved network analysis states from serialized objects. The underlying technical mechanism involves Python's pickle module, which allows for arbitrary object instantiation during deserialization. When an attacker supplies a maliciously crafted .pkl.gz file through the -s command line option or by configuring conf.session, the application processes this input without adequate validation of its contents. This lack of sanitization enables the execution of embedded Python code via the _reduce_ method, which is invoked automatically during unpickling to reconstruct objects. By exploiting this behavior, a remote attacker can achieve arbitrary code execution on the target system with the privileges of the user running Scapy.

From an operational perspective, this vulnerability allows for severe impact including full system compromise, data exfiltration, and lateral movement within affected networks. Since Scapy is often used by security professionals and network administrators to analyze traffic or craft packets, users may inadvertently load session files from untrusted sources under the assumption that they are safe configuration backups. The exploitation does not require complex interaction beyond convincing a user to open a specific file type, making it highly effective in social engineering scenarios where malicious payloads are disguised as legitimate session data. This aligns with common attack patterns observed in real-world incidents involving trusted software utilities being weaponized through supply chain or file-based vectors.

The technical classification of this flaw corresponds directly to CWE-502, which denotes Deserialization of Untrusted Data. It also maps to MITRE ATT&CK technique T1647, specifically the sub-category of Privilege Escalation via Trusted Software, as well as general code execution patterns associated with insecure deserialization in Python environments. The vulnerability highlights the inherent dangers of using pickle for data serialization when untrusted inputs are involved, a principle widely recognized in secure coding guidelines that recommend against its use for any external or network-received data without rigorous integrity checks and alternative safe formats like JSON or Protocol Buffers.

To mitigate this risk, organizations should immediately upgrade Scapy to version 2.7.0 or later where the vulnerability has been addressed through improved input validation and safer deserialization practices. Until an update is applied, users must exercise extreme caution when loading session files from any source that cannot be fully verified for authenticity and integrity. Implementing strict file type restrictions and validating checksums before processing can reduce exposure. Additionally, running Scapy with minimal privileges limits the potential impact of successful exploitation by restricting the scope of code execution to a non-privileged user context rather than full system access.

Responsible

VulnCheck

Reservation

11/13/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00242

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!