# Catastrophic backtracking in regex allows Denial of Service in Waitress

Advisory record · `GHSA-73m2-3pwg-5fgc`

- **Identifiers:** `GHSA-73m2-3pwg-5fgc` · `CVE-2020-5236` · `PYSEC-2020-155`
- **State:** Confirmed
- **Severity:** CVSS 5.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 4 Feb 2020
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Feb 2020, 03:07 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `waitress` (PyPI): affected `>=1.4.2, <1.4.3`; fixed in `1.4.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Waitress versions 1.4.2 up to but not including 1.4.3 are vulnerable to a regular expression denial of service. A single request containing a header with invalid characters can cause the regex engine to backtrack catastrophically, pinning the CPU at 100% and blocking other requests, which can take the service offline. Upgrade to waitress 1.4.3, which updates the header validation regex. A reverse proxy that rejects invalid headers may mitigate the issue until then.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.7 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.024, the 84th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:37 UTC: First seen by agentprime
- 31 Oct 2026, 14:37 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-73m2-3pwg-5fgc)

## Sources

- [GitHub Advisory Database: GHSA-73m2-3pwg-5fgc](https://github.com/advisories/GHSA-73m2-3pwg-5fgc)
- [OSV: GHSA-73m2-3pwg-5fgc](https://osv.dev/vulnerability/GHSA-73m2-3pwg-5fgc)
- <https://github.com/Pylons/waitress/security/advisories/GHSA-73m2-3pwg-5fgc>
- <https://nvd.nist.gov/vuln/detail/CVE-2020-5236>
- <https://github.com/Pylons/waitress/commit/6e46f9e3f014d64dd7d1e258eaf626e39870ee1f>
- <https://github.com/Pylons/waitress>
- <https://github.com/pypa/advisory-database/tree/main/vulns/waitress/PYSEC-2020-155.yaml>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-73m2-3pwg-5fgc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-73m2-3pwg-5fgc/>. Everything for agents: <https://agentprime.io/llms.txt>.
