# CVE-2026-128237: Scapy before 2.8.0 Denial of Service via Quadratic BER OID Decoding


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-128237, GHSA-f9f8-xrcx-w6x5, GHSA-xx44-g48m-mjp6, UBUNTU-CVE-2026-128237

## What is CVE-2026-128237?

CVE-2026-128237 is a medium-severity vulnerability in secdev scapy, published on 13 Nov 2026. 

### Official description

Scapy before 2.8.0 contains a denial of service vulnerability in BER_num_dec() and BERcodec_OID.do_dec() that allows remote attackers to exhaust CPU by supplying oversized OID arcs. Attackers can send ASN.1/BER data with many base-128 continuation bytes to cause quadratic CPU consumption or an uncaught ValueError crash on Python 3.11+.

Weakness: CWE-407 (Inefficient Algorithmic Complexity)

## Which versions are affected by CVE-2026-128237?

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


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

## How do I fix CVE-2026-128237?

Upgrade scapy to 2.8.0 or later.

## Is CVE-2026-128237 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-128237 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128237 and fix it if it is affected.

What it is: CVE-2026-128237 is a medium-severity vulnerability in secdev scapy, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-128237 exists.

Affected packages and fixed versions:
- scapy (PyPI): affected all versions; fixed in 2.8.0

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.
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-2026-128237/ (Markdown: https://insights.sbomify.com/CVE-2026-128237/index.md)
```

## Sources

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

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