# GHSA-92hv-j533-69wc: Wagtail: Identification of documents by SHA1 hash

> Attackers can determine if specific documents exist in Wagtail by comparing SHA1 hashes via HTTP headers, bypassing permission restrictions.

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

## What is GHSA-92hv-j533-69wc?

GHSA-92hv-j533-69wc is a vulnerability in wagtail, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Impact
By passing specific HTTP headers to the document serve URL endpoint, an attacker was able to determine whether a document with a given ID matched a specified SHA1 hash, regardless of any permission restrictions on the document or knowing its filename. This could allow an attacker to determine whether a document with a specific known hash is present in the Wagtail document library.

This vulnerability does not expose the document's contents or any metadata beyond the already known SHA1 hash, and does not expose information about any documents for which the attacker does not know the SHA1 hash.

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

### Workarounds
Site owners who are unable to upgrade can strip `If-Match` and `If-None-Match` from anonymous requests to `/documents/` at the reverse proxy, or use a custom document model without a `file_hash` attribute.

### Acknowledgements
Many thanks to Anand Himanshu 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-92hv-j533-69wc?

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-92hv-j533-69wc?

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

## Is GHSA-92hv-j533-69wc being exploited?

There is no known exploitation of GHSA-92hv-j533-69wc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-92hv-j533-69wc and fix it if it is affected.

What it is: GHSA-92hv-j533-69wc is a vulnerability in wagtail, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-92hv-j533-69wc 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-92hv-j533-69wc/ (Markdown: https://insights.sbomify.com/GHSA-92hv-j533-69wc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-92hv-j533-69wc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-92hv-j533-69wc/
Summaries are generated and may contain mistakes; the official description above is the record.