How severe is CVE-2026-25517?

No CVSS score has been assigned to CVE-2026-25517 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-25517?

CVE-2026-25517 affects the following packages: wagtail (PyPI), wagtail (PyPI), wagtail (PyPI), wagtail (PyPI), wagtail (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-25517?

Update wagtail to 6.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25517 is resolved across your whole dependency graph.

How do I detect CVE-2026-25517 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wagtail, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-25517 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-25517 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-25517 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-25517?

CVE-2026-25517 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-25517?

CVE-2026-25517 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-25517 published, and has it been updated?

CVE-2026-25517 was published on February 4, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-25517 — wagtail

Fix: wagtail/wagtail@01fd347

CVE-2026-25517 is a CWE-862 vulnerability in wagtail. A fix is available for wagtail — see the affected versions and patch details below.

Wagtail has improper permission handling on admin preview endpoints

Also known asGHSA-4qvv-g3vr-m348PYSEC-2026-2030

Published

Feb 4, 2026

Updated

Oct 28, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25517.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

5 pkgs affected

🐍wagtail🐍wagtail🐍wagtail🐍wagtail🐍wagtail

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Due to a missing permission check on the preview endpoints, a user with access to the Wagtail admin and knowledge of a model's fields can craft a form submission to obtain a preview rendering of any page, snippet or site setting object for which previews are enabled, consisting of any data of the user's choosing. The existing data of the object itself is not exposed, but depending on the nature of the template being rendered, this may expose other database contents that would otherwise only be accessible to users with edit access over the model. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.

Patches

Patched versions have been released as Wagtail 6.3.6, 7.0.4, 7.1.3 and 7.2.2. The new 7.3 feature release also incorporates this fix.

Workarounds

No workaround is available.

Acknowledgements

Many thanks to @thxtech 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 [email protected] (view our security policy for more information).

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`wagtail`	all versions	6.3.6`pip install --upgrade 'wagtail==6.3.6'`
🐍PyPI	`wagtail`	≥ 6.4rc1&&< 7.0.4	7.0.4`pip install --upgrade 'wagtail==7.0.4'`
🐍PyPI	`wagtail`	≥ 7.1rc1&&< 7.1.3	7.1.3`pip install --upgrade 'wagtail==7.1.3'`
🐍PyPI	`wagtail`	≥ 7.2rc1&&< 7.2.2	7.2.2`pip install --upgrade 'wagtail==7.2.2'`
🐍PyPI	`wagtail`	≥ 7.3rc1&&< 7.3	7.3`pip install --upgrade 'wagtail==7.3'`

Affected Products

1 product · 4 configurations

Application

wagtailtorchbox

≥ 7.2 && < 7.2.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wagtail, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wagtail to 6.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25517 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact Due to a missing permission check on the preview endpoints, a user with access to the Wagtail admin and knowledge of a model's fields can craft a form submission to obtain a preview rendering of any page, snippet or site setting object for which previews are enabled, consisting of any data of the user's choosing. The existing data of the object itself is not exposed, but depending on the nature of the template being rendered, this may expose other database contents that would otherwise only be accessible to users with edit access over the model. The vulnerability is not exploitable

O3 Security · Impact-Aware SCA

Is CVE-2026-25517 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works