VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

wagtail: vulnerability history, versions and safety

wagtail is a package in the PyPI ecosystem. Vulert records 56 vulnerabilities for it across 120 releases, from Apr 2020 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
56 vulnerabilities recorded H5 M22 L3 U26
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
34 in the last 12 months

Most recent disclosure 10 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all wagtail vulnerabilities

Vulert verdict on wagtail 8.0.1 i

Updated on 23 Oct 2026

Action needed: 8.0.1 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 66/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 8.0.1 — affected i
  • Vulnerabilities on record 56 over 6 years · 34 in the last year i
  • Latest disclosure 10 Sep 2026 i
  • Highest CVSS 7.3 i
  • With no published fix 0 i
  • Depended on by 401 packages i
  • Stars 20,573 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for wagtail, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
8.1.0rc1 21 Oct 2026 U2 BSD-3-Clause Yes Details →
8.0.1 20 Oct 2026 U2 BSD-3-Clause Yes Details →
7.4.4 20 Oct 2026 U2 BSD-3-Clause Yes Details →
7.0.10 20 Oct 2026 U2 BSD-3-Clause Yes Details →
8.0.0 25 Aug 2026 U2 BSD-3-Clause Yes Details →
8.0.0rc2 20 Aug 2026 U2 BSD-3-Clause Yes Details →
7.4.3 20 Aug 2026 U2 BSD-3-Clause Yes Details →
7.3.4 20 Aug 2026 U2 BSD-3-Clause Yes Details →
7.0.9 20 Aug 2026 U2 BSD-3-Clause Yes Details →
8.0.0rc1 13 Aug 2026 U2 BSD-3-Clause Yes Details →
7.4.2 15 Jun 2026 U1 BSD-3-Clause Yes Details →
7.3.3 15 Jun 2026 U1 BSD-3-Clause Yes Details →
7.0.8 15 Jun 2026 M4 L1 U1 BSD-3-Clause Yes Details →
7.4.1 19 May 2026 U6 BSD-3-Clause Yes Details →
7.4.0 05 May 2026 U2 BSD-3-Clause Yes Details →
7.3.2 05 May 2026 H1 U6 BSD-3-Clause Yes Details →
7.0.7 05 May 2026 M8 L1 U5 BSD-3-Clause Yes Details →
7.4.0rc1 22 Apr 2026 U2 BSD-3-Clause Yes Details →
7.3.1 03 Mar 2026 H1 U11 BSD-3-Clause Yes Details →
7.2.3 03 Mar 2026 U10 BSD-3-Clause Yes Details →
7.0.6 03 Mar 2026 M13 L1 U10 BSD-3-Clause Yes Details →
6.3.8 03 Mar 2026 M13 L1 U10 non-standard Yes Details →
7.0.5 12 Feb 2026 M13 L1 U12 BSD-3-Clause Yes Details →
6.3.7 12 Feb 2026 M15 L1 U12 non-standard Yes Details →
7.3.0 03 Feb 2026 H1 U3 BSD-3-Clause Yes Details →
7.2.2 03 Feb 2026 U12 BSD-3-Clause Yes Details →
7.1.3 03 Feb 2026 U12 BSD-3-Clause Yes Details →
7.0.4 03 Feb 2026 M13 L1 U12 BSD-3-Clause Yes Details →
6.3.6 03 Feb 2026 M15 L1 U12 non-standard Yes Details →
7.3.0rc1 21 Jan 2026 H1 U3 BSD-3-Clause Yes Details →
7.2.1 26 Nov 2025 U13 BSD-3-Clause Yes Details →
7.2.0 05 Nov 2025 U2 BSD-3-Clause Yes Details →
7.2.0rc1 23 Oct 2025 U2 BSD-3-Clause Yes Details →
7.1.2 23 Oct 2025 U13 BSD-3-Clause Yes Details →
7.1.1 28 Aug 2025 U13 BSD-3-Clause Yes Details →
7.0.3 28 Aug 2025 M13 L1 U13 BSD-3-Clause Yes Details →
7.1.0 04 Aug 2025 U2 BSD-3-Clause Yes Details →
7.1.0rc1 24 Jul 2025 U2 BSD-3-Clause Yes Details →
7.0.2 24 Jul 2025 M13 L1 U13 BSD-3-Clause Yes Details →
6.2.4 17 Jun 2025 M16 L1 U13 non-standard Yes Details →
7.0.1 12 Jun 2025 M13 L1 U13 BSD-3-Clause Yes Details →
6.4.2 12 Jun 2025 M13 L1 U13 non-standard Yes Details →
6.3.5 12 Jun 2025 M16 L1 U13 non-standard Yes Details →
7.0.0 06 May 2025 M13 L1 U12 BSD-3-Clause Yes Details →
7.0.0rc1 24 Apr 2025 M13 L1 U12 BSD-3-Clause Yes Details →
6.3.4 24 Apr 2025 M16 L1 U13 non-standard Yes Details →
6.4.1 21 Feb 2025 M13 L1 U13 non-standard Yes Details →
6.4.0 03 Feb 2025 M13 L1 U12 non-standard Yes Details →
6.3.3 03 Feb 2025 M16 L1 U13 non-standard Yes Details →
5.2.8 03 Feb 2025 M16 L1 U13 non-standard Yes Details →
6.4.0rc1 20 Jan 2025 M13 L1 U12 non-standard Yes Details →
6.3.2 02 Jan 2025 M16 L1 U13 non-standard Yes Details →
6.3.1 19 Nov 2024 M16 L1 U13 non-standard Yes Details →
6.3.0 01 Nov 2024 M16 L1 U15 non-standard Yes Details →
6.2.3 01 Nov 2024 M16 L1 U13 non-standard Yes Details →
5.2.7 01 Nov 2024 M16 L1 U13 non-standard Yes Details →
6.3.0rc2 21 Oct 2024 M16 L1 U15 non-standard Yes Details →
6.3.0rc1 21 Oct 2024 M16 L1 U15 non-standard Yes Details →
6.2.2 24 Sep 2024 M16 L1 U13 non-standard Yes Details →
6.2.1 20 Aug 2024 M16 L1 U13 non-standard Yes Details →
6.2.0 01 Aug 2024 M16 L1 U15 non-standard Yes Details →
6.2.0rc1 19 Jul 2024 M16 L1 U15 non-standard Yes Details →
6.1.3 11 Jul 2024 M16 L1 U13 non-standard Yes Details →
6.0.6 11 Jul 2024 M16 L1 U13 non-standard Yes Details →
5.2.6 11 Jul 2024 M16 L1 U13 non-standard Yes Details →
6.0.5 30 May 2024 H1 M16 L1 U14 non-standard Yes Details →
6.1.2 30 May 2024 M16 L1 U14 non-standard Yes Details →
6.1.1 21 May 2024 M16 L1 U15 non-standard Yes Details →
6.0.4 21 May 2024 H1 M17 L1 U15 non-standard Yes Details →
6.1.0 01 May 2024 M16 L1 U15 non-standard Yes Details →
6.0.3 01 May 2024 H1 M17 L1 U15 non-standard Yes Details →
5.2.5 01 May 2024 M16 L1 U14 non-standard Yes Details →
6.1.0rc2 25 Apr 2024 M16 L1 U15 non-standard Yes Details →
6.1.0rc1 18 Apr 2024 M16 L1 U15 non-standard Yes Details →
6.0.2 03 Apr 2024 H1 M17 L2 U16 non-standard Yes Details →
5.2.4 03 Apr 2024 M16 L1 U14 non-standard Yes Details →
6.0.1 15 Feb 2024 H1 M17 L2 U16 non-standard Yes Details →
6.0.0 07 Feb 2024 H1 M17 L2 U17 non-standard Yes Details →
6.0.0rc1 24 Jan 2024 H1 M16 L1 U15 non-standard Yes Details →
5.2.3 23 Jan 2024 M16 L1 U14 non-standard Yes Details →
5.2.2 06 Dec 2023 M16 L1 U14 non-standard Yes Details →
5.2.1 16 Nov 2023 M16 L1 U14 non-standard Yes Details →
5.2.0 01 Nov 2023 M16 L1 U15 non-standard Yes Details →
5.2.0rc1 19 Oct 2023 M16 L1 U15 non-standard Yes Details →
5.1.3 19 Oct 2023 M16 L1 U14 non-standard Yes Details →
5.0.5 19 Oct 2023 M16 L1 U14 non-standard Yes Details →
4.1.9 19 Oct 2023 M16 L1 U14 non-standard Yes Details →
5.0.4 04 Oct 2023 M16 L1 U15 non-standard Yes Details →
4.1.8 28 Sep 2023 M16 L2 U15 non-standard Yes Details →
4.1.7 27 Sep 2023 M16 L2 U15 non-standard Yes Details →
5.1.2 25 Sep 2023 M16 L1 U15 non-standard Yes Details →
5.0.3 25 Sep 2023 M16 L1 U15 non-standard Yes Details →
5.1.1 14 Aug 2023 M16 L1 U15 non-standard Yes Details →
5.1.0 01 Aug 2023 M16 L1 U15 non-standard Yes Details →
5.1.0rc1 18 Jul 2023 M16 L1 U15 non-standard Yes Details →
5.0.2 21 Jun 2023 M16 L1 U15 non-standard Yes Details →
5.0.1 25 May 2023 M16 L1 U15 non-standard Yes Details →
4.2.4 25 May 2023 M16 L1 U15 non-standard Yes Details →
4.1.6 25 May 2023 M16 L2 U15 non-standard Yes Details →
5.0.0 02 May 2023 M16 L1 U15 non-standard Yes Details →
4.2.3 02 May 2023 M16 L1 U15 — Yes Details →
4.1.5 02 May 2023 M16 L2 U15 — Yes Details →
5.0.0rc1 20 Apr 2023 M16 L1 U15 — Yes Details →
4.1.4 03 Apr 2023 M16 L2 U15 — Yes Details →
4.2.2 03 Apr 2023 M16 L1 U15 — Yes Details →
4.2.1 13 Mar 2023 M17 L1 U17 — Yes Details →
4.1.3 13 Mar 2023 H1 M16 L2 U17 — Yes Details →
4.2.0 06 Feb 2023 M17 L1 U16 — Yes Details →
4.1.2 06 Feb 2023 H1 M16 L2 U17 — Yes Details →
4.2.0rc1 20 Jan 2023 M17 L1 U16 — Yes Details →
4.1.1 11 Nov 2022 H1 M16 L2 U17 — Yes Details →
4.1.0 01 Nov 2022 H1 M16 L2 U16 — Yes Details →
4.0.4 18 Oct 2022 H1 M16 L2 U17 — Yes Details →
4.1.0rc1 18 Oct 2022 H1 M16 L2 U16 — Yes Details →
4.0.3 18 Oct 2022 H1 M16 L2 U17 — Yes Details →
4.0.2 23 Sep 2022 H1 M16 L2 U17 — Yes Details →
2.16.3 05 Sep 2022 H1 M16 L2 U17 — Yes Details →
2.15.6 05 Sep 2022 H1 M16 L2 U17 — Yes Details →
4.0.1 05 Sep 2022 H1 M16 L2 U17 — Yes Details →
3.0.3 05 Sep 2022 H1 M16 L2 U17 — Yes Details →

The newest 120 of 304 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 6
  • 2021 4
  • 2022 2
  • 2023 6
  • 2024 4
  • 2026 34

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 34 of the 56 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for wagtail

The 5 most severe of 56 vulnerabilities recorded for this package

Search all 56 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-54263: Wagtail Reflected XSS Vulnerability in Dynamic Image URL Generator 7.3 high 7.3.3 01 Jul 2026
CVE-2026-54263: Wagtail Reflected XSS Vulnerability in Dynamic Image URL Generator 7.3 high 7.3.3 20 Aug 2026
CVE-2026-44197: Wagtail Improper Permission Handling in Revision Compare View 6.5 medium 7.0.7 08 May 2026
CVE-2026-44199: Wagtail Improper Permission Handling in Form Submission Deletion 6.5 medium 7.0.7 08 May 2026
CVE-2026-44200: Wagtail Improper Permission Handling in Page Copying 6.5 medium 7.0.7 08 May 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About wagtail

Is wagtail safe to use?

Vulert records 56 vulnerabilities for wagtail in PyPI: 0 critical, 5 high, 22 medium and 3 low, plus 26 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is wagtail's Vulert package health score?

Vulert scores wagtail 66/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of wagtail affected?

Yes. 8.0.1, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does wagtail have?

56 vulnerabilities are recorded for wagtail in the PyPI ecosystem: 0 critical, 5 high, 22 medium and 3 low, plus 26 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new wagtail vulnerabilities disclosed?

34 vulnerabilities were recorded for wagtail in the last 12 months, and the oldest entry in this database dates to 14 Apr 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of wagtail are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor wagtail for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the wagtail version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.