# CVE-2026-125106: Wagtail: Improper restriction handling on Page translation API endpoint


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-jm5p-837g-rv8g

## What is CVE-2026-125106?

CVE-2026-125106 is a medium-severity vulnerability in wagtail, published on 9 Nov 2026. 

### Official description

Wagtail is an open source content management system built on Django. Prior to 7.0.9, 7.3.4, 7.4.3, and 8.0rc2, a Wagtail CMS user with the submit translations permission can call the Admin API copy for translation action for a source page that the user cannot edit. The action copies the inaccessible page into a translation, allowing the user to view its contents despite the missing source-page edit permission. This issue is fixed in versions 7.0.9, 7.3.4, 7.4.3, and 8.0rc2.

Weakness: CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

## Which versions are affected by CVE-2026-125106?

4 open source packages ship an affected version, including wagtail.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wagtail` | PyPI | All versions | 7.0.9 |
| `wagtail` | PyPI | From 7.1rc1 | 7.3.4 |
| `wagtail` | PyPI | From 7.4rc1 | 7.4.3 |
| `wagtail` | PyPI | From 8.0rc1 | 8.0rc2 |

## How do I fix CVE-2026-125106?

Upgrade wagtail to a fixed version for your release line: 7.0.9, 7.3.4, 7.4.3 or 8.0rc2.

## Is CVE-2026-125106 being exploited?

There is no known exploitation of CVE-2026-125106 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125106 and fix it if it is affected.

What it is: CVE-2026-125106 is a medium-severity vulnerability in wagtail, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125106 in the wild and no public exploit code.

Affected packages and fixed versions:
- wagtail (PyPI): affected all versions; fixed in 7.0.9
- wagtail (PyPI): affected from 7.1rc1; fixed in 7.3.4
- wagtail (PyPI): affected from 7.4rc1; fixed in 7.4.3
- wagtail (PyPI): affected from 8.0rc1; fixed in 8.0rc2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125106/ (Markdown: https://insights.sbomify.com/CVE-2026-125106/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125106
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125106
- OSV: https://osv.dev/vulnerability/CVE-2026-125106

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125106/
Summaries are generated and may contain mistakes; the official description above is the record.