Quick answers
- Is CVE-2026-44201 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44201 being exploited in the wild.
- How severe is CVE-2026-44201?
- Medium severity, with a CVSS score of 5.3, published 11 May 2026.
- Which products and versions are affected?
- wagtail (PyPI) ECOSYSTEM:introduced=0,fixed=7.0.7, ECOSYSTEM:introduced=0,fixed=7.0.7,introduced=7.1,fixed=7.3.2; Wagtail < 7.0.7, >= 7.1, < 7.3.2, < 7.0.7, 7.1 - 7.3.1.
- Is there a fix for CVE-2026-44201?
- Yes. wagtail (PyPI): upgrade to 7.0.7, 7.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44201 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44201?
- Check whether you run wagtail (PyPI) or Wagtail at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- wagtail (PyPI): upgrade to 7.0.7, 7.3.2 or later
pip install "wagtail>=7.3.2"
Technical details
A vulnerability exists in Wagtail's Documents and Images API due to improper handling of insufficient permissions (CWE-280). The API incorrectly lists items belonging to private collections, exposing metadata such as filenames and document names to any user with API access. This is exploitable over the network without authentication if the API is configured without mandatory auth. The issue affects Wagtail versions prior to 7.0.7 and versions between 7.1 and 7.3.2. Patches are available in versions 7.0.7, 7.3.2, and 7.4 LTS. A temporary workaround is to enforce authentication on the affected API endpoints.
Affected products
- Wagtail Wagtail < 7.0.7, >= 7.1, < 7.3.2
Identifiers
- CVE-2026-44201
- GHSA-p5gm-92h4-6pv6
- PYSEC-2026-150
Timeline
- 2026-05-08: advisory: GitHub Advisory published
- 2026-05-08: patched: Wagtail 7.0.7 and 7.3.2 released