VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

scapy: vulnerability history, versions and safety

scapy is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 34 releases, from Jul 2019 to Oct 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M1 U2
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all scapy vulnerabilities

Vulert verdict on scapy 2.8.0 i

Updated on 23 Oct 2026

Careful: 2.8.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.8.0 — affected i
  • Vulnerabilities on record 4 over 6 years · 0 in the last year i
  • Latest disclosure 22 Oct 2025 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Depended on by 435 packages i
  • Stars 12,644 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence GPL-2.0-only i
  • Similar names scanpy, scipy, scrapy i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for scapy, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.8.0 02 Oct 2026 M1 GPL-2.0-only No Details →
2.7.1rc1 13 Apr 2026 M1 GPL-2.0-only No Details →
2.7.0 26 Dec 2025 M1 GPL-2.0-only No Details →
2.7.0rc1 02 Nov 2025 M1 GPL-2.0-only No Details →
2.6.1 05 Nov 2024 M1 GPL-2.0-only No Details →
2.6.0 28 Sep 2024 M1 GPL-2.0-only No Details →
2.6.0rc2 08 Sep 2024 M1 GPL-2.0-only No Details →
2.6.0rc1 28 Apr 2024 M1 GPL-2.0-only No Details →
2.5.0 25 Dec 2022 M1 GPL-2.0-only No Details →
2.5.0rc3 12 Dec 2022 M1 GPL-2.0-only No Details →
2.5.0rc2 04 Oct 2022 M1 GPL-2.0-only No Details →
2.5.0rc1 21 Aug 2022 M1 GPL-2.0-only No Details →
2.4.5 19 Apr 2021 M1 GPL-2.0 No Details →
2.4.5rc1 30 Mar 2021 M1 GPL-2.0 No Details →
2.4.4 02 Sep 2020 M1 GPL-2.0 No Details →
2.4.4rc2 26 Jul 2020 M1 GPL-2.0 No Details →
2.4.4rc1 19 Jul 2020 M1 GPL-2.0 No Details →
2.4.3 06 Aug 2019 M1 GPL-2.0 No Details →
2.4.3rc4 29 Jul 2019 M1 GPL-2.0 No Details →
2.4.3rc3 09 Jul 2019 M1 GPL-2.0 No Details →
2.4.3rc2 01 Jul 2019 M1 GPL-2.0 No Details →
2.4.3rc1 05 Mar 2019 M1 GPL-2.0 No Details →
2.4.2 10 Jan 2019 M1 GPL-2.0 No Details →
2.4.1 10 Jan 2019 M1 GPL-2.0 No Details →
2.4.0 27 Mar 2018 H1 M1 U2 GPL-2.0 No Details →
2.4.0rc5 01 Mar 2018 H1 M1 U2 GPL-2.0 No Details →
2.4.0rc4 28 Jan 2018 H1 M1 U2 GPL-2.0 No Details →
2.4.0rc3 17 Jan 2018 H1 M1 U2 GPL-2.0 No Details →
2.4.0rc2 10 Jan 2018 H1 M1 U2 GPL-2.0 No Details →
2.3.3 18 Oct 2016 M1 U2 GPL-2.0 No Details →
2.3.2 29 Jan 2016 M1 U2 GPL-2.0 No Details →
2.3.1 30 Dec 2014 M1 U2 GPL-2.0 No Details →
2.2.0.dev0 12 Oct 2013 M1 U2 GPL-2.0 No Details →
2.2.0-dev.linux-x86_64 — M1 U2 — No Details →

All 34 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 3
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for scapy

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-1010142: Denial of Service in scapy 7.5 high 2.4.1 22 Jul 2019
Arbitrary Code Execution Vulnerability in Scapy due to Unsafe Deserialization 5.4 medium No fix published 22 Oct 2025
CVE-2019-1010142: Denial of Service in scapy 2.4.0 N/A unrated 2.4.1 19 Jul 2019
CVE-2019-1010142: Denial of Service in scapy 2.4.0 N/A unrated 2.4.1 19 Jul 2019

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About scapy

Is scapy safe to use?

Vulert records 4 vulnerabilities for scapy in PyPI: 0 critical, 1 high, 1 medium and 0 low, plus 2 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is scapy's Vulert package health score?

Vulert scores scapy 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of scapy affected?

Yes. 2.8.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of scapy should I use?

2.8.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does scapy have?

4 vulnerabilities are recorded for scapy in the PyPI ecosystem: 0 critical, 1 high, 1 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new scapy vulnerabilities disclosed?

0 vulnerabilities were recorded for scapy in the last 12 months, and the oldest entry in this database dates to 19 Jul 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of scapy are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor scapy for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the scapy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.