Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

GHSA-mpf2-q34c-fc6j — scapy

HIGHFix: secdev/scapy#1409

GHSA-mpf2-q34c-fc6j is a high-severity (CVSS 7.5) CWE-835 vulnerability in scapy. 1 public exploit reference exists, so weaponization risk is real. A fix is available for scapy — see the affected versions and patch details below.

Infinite Loop in scapy

Also known asCVE-2019-1010142PYSEC-2019-120
Published
Jul 22, 2019
Updated
Oct 22, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-mpf2-q34c-fc6j by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐍scapy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

scapy is affected by a Denial of Service vulnerability resulting in an infinite loop and resource consumption rendering the program unresponsive. The component is: _RADIUSAttrPacketListField.getfield(self..). The attack vector is over the network or in a pcap. both work.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIscapy≥ 2.4-rc1&&< 2.4.12.4.1pip install --upgrade 'scapy==2.4.1'

Affected Products

2 products · 3 configurations
OS
fedorafedoraproject
2 versions
2930
Application
scapyscapy
1 version
2.4.0
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for scapy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update scapy to 2.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mpf2-q34c-fc6j is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

scapy is affected by a Denial of Service vulnerability resulting in an infinite loop and resource consumption rendering the program unresponsive. The component is: `_RADIUSAttrPacketListField.getfield(self..)`. The attack vector is over the network or in a pcap. both work.
O3 Security · Impact-Aware SCA

Is GHSA-mpf2-q34c-fc6j in your dependencies?

Find it across PyPI, including transitive dependencies.

GHSA-mpf2-q34c-fc6j: scapy DoS (High 7.5) | O3 Security