How do I fix "ModuleNotFoundError: No module named 'cgi'"?

Replace `cgi.parse_qs` with `urllib.parse.parse_qs`. Replace `cgi.escape` with `html.escape`. For multipart/form-data, use a maintained parser (e.g. `multipart`, `werkzeug`, or your web framework's). Upgrade dependencies that still import cgi, then re-test on Python 3.13. Source: https://docs.python.org/3/whatsnew/3.13.html

Python 3.13

ModuleNotFoundError: No module named 'cgi'

ModuleNotFoundError: No module named 'cgi'

What it means

The cgi and cgitb modules were removed in Python 3.13 (PEP 594, the 'dead batteries' cleanup).

Why it happens

cgi was deprecated in 3.11 and removed in 3.13. Code or a dependency still imports it — commonly for parse_qs or multipart parsing — and breaks after moving to a python3.13 runtime.

How to fix it

Replace `cgi.parse_qs` with `urllib.parse.parse_qs`.
Replace `cgi.escape` with `html.escape`.
For multipart/form-data, use a maintained parser (e.g. `multipart`, `werkzeug`, or your web framework's).
Upgrade dependencies that still import cgi, then re-test on Python 3.13.

Related deadline: Lambda Python 3.11 projected create/update restrictions — 2027-07-31.

Check configured patterns in your project

The free EOLkits scanner processes files in your browser and flags selected related patterns in supported IaC and dependency files. File names and contents are not uploaded; bounded aggregate file and finding counts may be sent. It is not a complete source or AWS-account scan.

Prefer a 10-second check? Paste your config into the free AWS EOL checker. Pasted input is not uploaded; bounded first-party usage events may be sent.

Primary source: https://docs.python.org/3/whatsnew/3.13.html

Inspect the $299 report sample and availability →