# GHSA-c2xx-cjmh-9q8f: Wagtail: Improper restriction handling on descendant collections in Documents and Images API

> An attacker with API access can view filenames and names of documents and images in private collections due to improper restriction handling.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2026

## What is GHSA-c2xx-cjmh-9q8f?

GHSA-c2xx-cjmh-9q8f is a missing authorization vulnerability in wagtail, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

### Impact

The Documents and Images [API V2](https://docs.wagtail.org/en/stable/advanced_topics/api/index.html) incorrectly listed items in descendants of private collections, which should inherit the view restrictions defined on their ancestors. A user with access to the API could see the filename and name of documents and images in these descendant collections.

### Patches

Patched versions have been released as Wagtail 7.0.9, 7.3.4, 7.4.3 and 8.0rc2.

### Workarounds

Site owners using Wagtail's API can avoid the vulnerability by adding [authentication](https://docs.wagtail.org/en/stable/advanced_topics/api/v2/configuration.html#authentication) to the Documents and Images APIs.

### Acknowledgements

Many thanks to Ta Duc Thien for reporting this issue.

### For more information
If you have any questions or comments about this advisory:

* Visit Wagtail's [support channels](https://docs.wagtail.org/en/stable/support.html)
* Email us at [security@wagtail.org](mailto:security@wagtail.org) (view our [security policy](https://github.com/wagtail/wagtail/security/policy) for more information).

## Which versions are affected by GHSA-c2xx-cjmh-9q8f?

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


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

## How do I fix GHSA-c2xx-cjmh-9q8f?

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

## Is GHSA-c2xx-cjmh-9q8f being exploited?

There is no known exploitation of GHSA-c2xx-cjmh-9q8f in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-c2xx-cjmh-9q8f and fix it if it is affected.

What it is: GHSA-c2xx-cjmh-9q8f is a missing authorization vulnerability in wagtail, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-c2xx-cjmh-9q8f 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 all versions; fixed in 7.0.9
- wagtail (PyPI): affected from 7.1; fixed in 7.3.4
- 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 7.4; fixed in 7.4.3
- wagtail (PyPI): affected from 8.0rc1; fixed in 8.0rc2
- 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/GHSA-c2xx-cjmh-9q8f/ (Markdown: https://insights.sbomify.com/GHSA-c2xx-cjmh-9q8f/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-c2xx-cjmh-9q8f

---
From sbomify Insights: https://insights.sbomify.com/GHSA-c2xx-cjmh-9q8f/
Summaries are generated and may contain mistakes; the official description above is the record.