Wagtail vulnerable to denial-of-service via memory exhaustion when uploading large files
Impact
A memory exhaustion bug exists in Wagtail's handling of uploaded images and documents. For both images and documents, files are loaded into memory during upload for additional processing. A user with access to upload images or documents through the Wagtail admin interface could upload a file so large that it results in a crash or denial of service.
The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. It can only be exploited by admin users with permission to upload images or documents.
Image uploads are restricted to 10MB by default, however this validation only happens on the frontend and on the backend after the vulnerable code.
Patches
Patched versions have been released as Wagtail 4.1.4 (for the LTS 4.1 branch) and Wagtail 4.2.2 (for the current 4.2 branch).
Workarounds
Site owners who are unable to upgrade to the new versions are encouraged to add extra protections outside of Wagtail to limit the size of uploaded files. Exactly how this is done will vary based on your hosting environment, but here are a few references for common setups:
- Nginx:
client_max_body_size - Apache:
LimitRequestBody - Cloudflare: Already imposes a limit of 100MB - 500MB depending on plan
- CloudFront:
SizeConstraint - Traefik:
traefik.http.middlewares.limit.buffering.maxRequestBodyBytes
The changes themselves are deep inside Wagtail, making patching incredibly difficult.
Czego dotyczy
Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.
| Platforma | Paczka | Podatne wersje | Poprawka w wersji |
|---|---|---|---|
| Python (PyPI) | wagtail | >= 4.2, < 4.2.2, < 4.1.4 | 4.2.2, 4.1.4 |
Odnośniki
- https://github.com/wagtail/wagtail/commit/cfa11bbe00dbe7ce8cd4c0bbfe2a898a690df2bf
- https://github.com/wagtail/wagtail/releases/tag/v4.2.2
- https://github.com/wagtail/wagtail/commit/3c0c64642b9e5b8d28b111263c7f4bddad6c3880
- https://github.com/wagtail/wagtail/security/advisories/GHSA-33pv-vcgh-jfg9
- https://docs.wagtail.org/en/stable/reference/settings.html#wagtailimages-max-upload-size
- https://github.com/wagtail/wagtail/commit/c9d2fcd650a88d76ae122646142245e5927a9165
- https://github.com/wagtail/wagtail/commit/d4022310cbe497993459c3136311467c7ac6329a
- https://github.com/wagtail/wagtail/releases/tag/v4.1.4
- https://nvd.nist.gov/vuln/detail/CVE-2023-28837
- https://github.com/pypa/advisory-database/tree/main/vulns/wagtail/PYSEC-2023-56.yaml
- https://github.com/wagtail/wagtail
- Wektor CVSS
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H- Słabość (CWE)
CWE-400, CWE-770- Platforma
- Python (PyPI)
- Paczka
wagtail- Ujawniono
- 03.04.2023
- Aktualizacja
- 11.10.2026 15:17
Źródła i licencje
OSV / GitHub Advisory Database - PYSEC-2023-56 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-33pv-vcgh-jfg9 - CC BY 4.0
Historia podatności: wagtail
Wszystkie opisane podatności tej paczki (Python (PyPI)), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 30
- Pierwsza → ostatnia
- 04.2020 08.2026
- Bez poprawki
- 0
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Wysoka 5
- Średnia 22
- Niska 3
Ujawnienia w latach
- 2020: 3
- 2021: 2
- 2022: 1
- 2023: 3
- 2024: 3
- 2025: 0
- 2026: 18
-
Wagtail vulnerable to denial-of-service via memory exhaustion when uploading large files ten wpis
Dowiedz się, które podatności dotyczą Twojej aplikacji
Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.