Vulnerability in wagtail (CVE-2026-55468)
Summary
Vulnerability in wagtail (CVE-2026-55468). Risk of unauthorized operations or information disclosure. Exploitable via api_fields. Mitigation: upgrade to 8.0rc2 or later.
Original description
The description as published by the source.
Impact
The internal Pages admin API incorrectly returns page fields without access control when they are declared in api_fields. A user with access to the Wagtail admin can use this API to fetch draft and live page fields’ contents that are part of api_fields on the base page model (title, slug, seo_title, search_description), as well as all custom fields declared in api_fields.
The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.
Patches
Patched versions have been released as Wagtail 7.0.9, 7.3.4, 7.4.3 and 8.0rc2.
Workarounds
Site owners unable to upgrade can apply the fix by overriding the relevant method on PagesAdminAPIViewSet to patch all vulnerable admin API endpoints:
# wagtail_hooks.py or AppConfig.ready()
from wagtail.admin.api.views import PagesAdminAPIViewSet
from wagtail.permissions import page_permission_policy
def _restricted_get_base_queryset(self):
return page_permission_policy.explorable_instances(self.request.user)
PagesAdminAPIViewSet.get_base_queryset = _restricted_get_base_queryset
Acknowledgements
Many thanks to xuliang@QAX for reporting this issue.
For more information
If you have any questions or comments about this advisory:
- Visit Wagtail's support channels
- Email us at [security@wagtail.org](mailto:security@wagtail.…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55468 has been found in wagtail.
Attackers can target a specific entry point like api_fields over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade wagtail to 8.0rc2 or later.
If unsure, ask your IT team or search "wagtail CVE-2026-55468" on the vendor's site.
CVE-2026-55468 (wagtail) — CWE-280 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: api_fields / PagesAdminAPIViewSet
Patched: 8.0rc2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-280) exists in wagtail. Attackers reach the vulnerable code path via api_fields.
Check the vendor advisory for the affected versions of wagtail. Attack surface: api_fields / PagesAdminAPIViewSet.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 8.0rc2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wagtail' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wagtail' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wagtailを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade wagtail to 8.0rc2ステージング環境で 8.0rc2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。