{"items":[{"id":"NVI-00014097","kind":"vulnerability","title":"Wagtail: Identification of documents by SHA1 hash","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-92hv-j533-69wc"],"plain_summary":"GitHub lists this reviewed advisory for wagtail, wagtail, wagtail, wagtail. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-44f45d2d7a217ef2fb45b6a60b767f56"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-20T19:50:00.000Z","value":"3.7 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-44f45d2d7a217ef2fb45b6a60b767f56"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-44f45d2d7a217ef2fb45b6a60b767f56","url":"https://github.com/advisories/GHSA-92hv-j533-69wc","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-92hv-j533-69wc","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T09:56:46.713Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-44f45d2d7a217ef2fb45b6a60b767f56"],"technology":"wagtail","known_exclusions":[],"conditions_summary":"### Impact\nBy 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.\n\nThis 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.\n\n### Patches\nPatched versions have been released as Wagtail 7.0.9, 7.3.4, 7.4.3 and 8.0rc2.\n\n### Workarounds\nSite 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.\n\n### Acknowledgements\nMany thanks to Anand Himanshu for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Visit Wagtail's support channels\n* Email us at [security@","public_affected_ranges":["< 7.0.9"]},{"certainty":"source_listed","source_ids":["sr-44f45d2d7a217ef2fb45b6a60b767f56"],"technology":"wagtail","known_exclusions":[],"conditions_summary":"### Impact\nBy 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.\n\nThis 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.\n\n### Patches\nPatched versions have been released as Wagtail 7.0.9, 7.3.4, 7.4.3 and 8.0rc2.\n\n### Workarounds\nSite 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.\n\n### Acknowledgements\nMany thanks to Anand Himanshu for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Visit Wagtail's support channels\n* Email us at [security@","public_affected_ranges":[">= 7.1, < 7.3.4"]},{"certainty":"source_listed","source_ids":["sr-44f45d2d7a217ef2fb45b6a60b767f56"],"technology":"wagtail","known_exclusions":[],"conditions_summary":"### Impact\nBy 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.\n\nThis 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.\n\n### Patches\nPatched versions have been released as Wagtail 7.0.9, 7.3.4, 7.4.3 and 8.0rc2.\n\n### Workarounds\nSite 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.\n\n### Acknowledgements\nMany thanks to Anand Himanshu for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Visit Wagtail's support channels\n* Email us at [security@","public_affected_ranges":[">= 7.4, < 7.4.3"]},{"certainty":"source_listed","source_ids":["sr-44f45d2d7a217ef2fb45b6a60b767f56"],"technology":"wagtail","known_exclusions":[],"conditions_summary":"### Impact\nBy 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.\n\nThis 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.\n\n### Patches\nPatched versions have been released as Wagtail 7.0.9, 7.3.4, 7.4.3 and 8.0rc2.\n\n### Workarounds\nSite 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.\n\n### Acknowledgements\nMany thanks to Anand Himanshu for reporting this issue.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n* Visit Wagtail's support channels\n* Email us at [security@","public_affected_ranges":["= 8.0rc1"]}],"null_published_at":"2026-11-02T10:00:37.206Z","source_updated_at":"2026-08-20T19:50:00.000Z","source_disclosed_at":"2026-08-20T18:45:09.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-02T09:56:46.713Z"}],"next_cursor":null,"snapshot_revision":"42594"}