<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T21:05:31.140847+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2024-39317</id>
    <title>CVE-2024-39317 — Wagtail regular expression denial-of-service via search query parsing</title>
    <updated>2026-10-04T21:05:31.142579+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> wagtail</p>
<p>Wagtail is an open source content management system built on Django. A bug in Wagtail's `parse_query_string` would result in it taking a long time to process suitably crafted inputs. When used to parse sufficiently long strings of characters without a space, `parse_query_string` would take an unexpectedly large amount of time to process, resulting in a denial of service. In an initial Wagtail installation, the vulnerability can be exploited by any Wagtail admin user. It cannot be exploited by end users. If your Wagtail site has a custom search implementation which uses `parse_query_string`, it may be exploitable by other users (e.g. unauthenticated users). Patched versions have been released as Wagtail 5.2.6, 6.0.6 and 6.1.3.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2024-39317"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-jmp3-39vp-fwg8</id>
    <title>GHSA-jmp3-39vp-fwg8 — Wagtail regular expression denial-of-service via search query parsing</title>
    <updated>2026-10-04T21:05:31.142638+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: wagtail</p>
<p>### Impact</p>
<p>A bug in Wagtail's [`parse_query_string`](https://docs.wagtail.org/en/stable/topics/search/searching.html#wagtailsearch-query-string-parsing) would result in it taking a long time to process suitably crafted inputs. When used to parse sufficiently long strings of characters without a space, `parse_query_string` would take an unexpectedly large amount of time to process, resulting in a denial of service.</p>
<p>In an initial Wagtail installation, the vulnerability can be exploited by any Wagtail admin user. It cannot be exploited by end users. If your Wagtail site has a custom search implementation which uses `parse_query_string`, it may be exploitable by other users (e.g. unauthenticated users).</p>
<p>### Patches</p>
<p>Patched versions have been released as Wagtail 5.2.6, 6.0.6 and 6.1.3.</p>
<p>This vulnerability affects all unpatched versions from Wagtail 2.0 onwards.</p>
<p>### Workarounds</p>
<p>Site owners who are unable to upgrade to a patched version can limit the length of search terms passed to `parse_query_string`. Whilst the performance characteristics will depend on your hosting environment, 1000 characters has been shown to still be fairly fast, without triggering this vulnerability.</p>
<p>No workaround is available for the Wagtail admin usage.</p>
<p>### Acknowledgements</p>
<p>Many thanks to [Jake Howard](https://github.com/RealOrangeOne) for reporting this issue.</p>
<p>### For more information
If you have any questions or comments about this advisory:</p>
<p>* Visit Wagtail's [support channels](https://docs.…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-jmp3-39vp-fwg8"/>
  </entry>
</feed>
