Staging Environment: Content and features may be unstable or change without notice.

Advisory Package Curation

CVE-2026-44197

Progress 0 / 0

Advisory Summaries

github_osv/GHSA-c6wj-9vcj-75pj

Wagtail has improper permission handling when comparing revisions ### Impact A CMS user without the ability to edit a page could access revisions of the page through the revision compare view if they knew the primary key of two revisions. This could potentially result in disclosure of sensitive information. ### 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 No workaround is available. ### Acknowledgements Many thanks to Seoyoung Kang @seoyoung-kang from AhnLab and an independent security researcher for reporting this issue. ### For more information If there are any questions or comments about this advisory: * Visit Wagtail's support channels https://docs.wagtail.org/en/stable/support.html * Send an email to [security@wagtail.org](mailto:security@wagtail.org) (view the security policy https://github.com/wagtail/wagtail/security/policy for more information).

gitlab/pypi/wagtail/CVE-2026-44197

Wagtail has improper permission handling when comparing revisions A CMS user without the ability to edit a page could access revisions of the page through the revision compare view if they knew the primary key of two revisions. This could potentially result in disclosure of sensitive information.

pypa/wagtail/PYSEC-2026-146

Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user without the ability to edit a page could access revisions of the page through the revision compare view if they knew the primary key of two revisions. This could potentially result in disclosure of sensitive information. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.

pysec/PYSEC-2026-146

Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user without the ability to edit a page could access revisions of the page through the revision compare view if they knew the primary key of two revisions. This could potentially result in disclosure of sensitive information. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.