CVE-2026-44201: Wagtail: Improper restriction handling on Documents and Images API
Impact
The Documents and Images API incorrectly listed items in private collections. A user with access to the API could see the filename and name of documents and images in private collections.
Patches
Patched versions have been released as Wagtail 7.0.7 and 7.3.2. The new 7.4 LTS feature release also incorporates this fix.
Workarounds
Site owners using Wagtail's API can avoid the vulnerability by adding authentication to the Documents and Images APIs.
Acknowledgements
Wagtail thanks independent security researcher Sanjok Karki @thesanjok for reporting this issue.
For more information If there are any questions or comments about this advisory:
Visit Wagtail's support channels Send an email to security@wagtail.org (view the security policy for more information).
Other sources
Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, the Documents and Images API incorrectly listed items in private collections. A user with access to the API could see the filename and name of documents and images in private collections. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44201?
CVE-2026-44201 is classified as a medium severity vulnerability due to unauthorized access to private collections.
How do I fix CVE-2026-44201?
To fix CVE-2026-44201, upgrade to Wagtail version 7.3.2 or 7.0.7.
What is the impact of CVE-2026-44201?
CVE-2026-44201 allows users with API access to view filenames and names of documents and images from private collections.
Which versions of Wagtail are affected by CVE-2026-44201?
Wagtail versions between 7.1 and 7.3.2, as well as versions up to 7.0.7, are affected by CVE-2026-44201.
Who is at risk from CVE-2026-44201?
Users with API access to Wagtail who have permission to see private collections are at risk from CVE-2026-44201.