Quick answers
- Is CVE-2026-44198 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44198 being exploited in the wild.
- How severe is CVE-2026-44198?
- Medium severity, with a CVSS score of 4.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-44198?
- 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-44198 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44198?
- 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
An improper authorization vulnerability (CWE-280) exists in Wagtail's page history reporting component. The application fails to correctly verify that a user has 'edit' permissions before granting access to the history report for a specific page. An authenticated CMS user with low privileges can exploit this over the network to view historical revisions, potentially disclosing sensitive information stored in older versions of content. The issue is resolved in Wagtail versions 7.0.7, 7.3.2, and 7.4 LTS.
Affected products
- Wagtail Wagtail < 7.0.7, >= 7.1, < 7.3.2
Identifiers
- CVE-2026-44198
- GHSA-c4mr-889m-vgf6
- PYSEC-2026-147
Timeline
- 2026-05-05: disclosed: Initial disclosure by Wagtail maintainers
- 2026-05-08: advisory: GitHub Advisory published
- 2026-05-11: other: NVD publication date