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.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Python (PyPI) | wagtail | >= 4.2, < 4.2.2, < 4.1.4 | 4.2.2, 4.1.4 |
Referencias
- 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
- Vector CVSS
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H- Debilidad (CWE)
CWE-400, CWE-770- Plataforma
- Python (PyPI)
- Paquete
wagtail- Publicada
- 03.04.2023
- Actualizado
- 11.10.2026 15:17
Fuentes y licencias
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
Historial de vulnerabilidades: wagtail
Todas las vulnerabilidades publicadas de este paquete (Python (PyPI)), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 30
- Primera → última
- 04.2020 08.2026
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Alta 5
- Media 22
- Baja 3
Divulgaciones por año
- 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 esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.