# CVE-2026-123820: Wagtail: Improper restriction handling on descendant collections in Documents and Images API


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-c2xx-cjmh-9q8f

## What is CVE-2026-123820?

CVE-2026-123820 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, the Wagtail Documents and Images API V2 excludes directly restricted collections but fails to exclude their descendant collections, even though descendants inherit ancestor view restrictions. An API user can therefore list the filenames and names of documents and images stored in descendant collections that should remain private. 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-123820?

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.1 | 7.3.4 |
| `wagtail` | PyPI | From 7.4 | 7.4.3 |
| `wagtail` | PyPI | From 8.0rc1 | 8.0rc2 |

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

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-123820 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123820 is a medium-severity vulnerability in wagtail, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123820 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.1; fixed in 7.3.4
- wagtail (PyPI): affected from 7.4; 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-123820/ (Markdown: https://insights.sbomify.com/CVE-2026-123820/index.md)
```

## Sources

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

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