<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 16 Oct 2026 21:23:20 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-108981</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-108981</link>
      <description>&lt;p&gt;ngx_cache_purge before 3.0.4 can allow file deletion via a symlink attack in certain situations where nginx and a served application (e.g., WordPress) run under the same user account. The attacker must be able to create a symlink inside the cache path. Version 3.0.4 fixes this for the case of a symlink created at an arbitrary earlier time, but does not resolve an applicable TOCTOU race condition. (The ngx_cache_purge module follows symlinks while walking the cache directory tree during purge operations. The module relies on nginx&amp;#39;s ngx_walk_tree(), which relies on stat() and therefore follows symlinks.)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ngx_cache_purge before 3.0.4 can allow file deletion via a symlink attack in certain situations where nginx and a served application (e.g., WordPress) run under the same user account. The attacker must be able to create a symlink inside the cache path. Version 3.0.4 fixes this for the case of a symlink created at an arbitrary earlier time, but does not resolve an applicable TOCTOU race condition. (The ngx_cache_purge module follows symlinks while walking the cache directory tree during purge operations. The module relies on nginx&amp;#39;s ngx_walk_tree(), which relies on stat() and therefore follows symlinks.)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-108981</guid>
    </item>
    <item>
      <title>GHSA-5fhq-3m7h-fqv8</title>
      <link>https://db.gcve.eu/vuln/ghsa-5fhq-3m7h-fqv8</link>
      <description>&lt;p&gt;ngx_cache_purge before 3.0.4 can allow file deletion via a symlink attack in certain situations where nginx and a served application (e.g., WordPress) run under the same user account. The attacker must be able to create a symlink inside the cache path. Version 3.0.4 fixes this for the case of a symlink created at an arbitrary earlier time, but does not resolve an applicable TOCTOU race condition. (The ngx_cache_purge module follows symlinks while walking the cache directory tree during purge operations. The module relies on nginx&amp;#39;s ngx_walk_tree(), which relies on stat() and therefore follows symlinks.)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ngx_cache_purge before 3.0.4 can allow file deletion via a symlink attack in certain situations where nginx and a served application (e.g., WordPress) run under the same user account. The attacker must be able to create a symlink inside the cache path. Version 3.0.4 fixes this for the case of a symlink created at an arbitrary earlier time, but does not resolve an applicable TOCTOU race condition. (The ngx_cache_purge module follows symlinks while walking the cache directory tree during purge operations. The module relies on nginx&amp;#39;s ngx_walk_tree(), which relies on stat() and therefore follows symlinks.)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-5fhq-3m7h-fqv8</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-108981</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-108981</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: libnginx-mod-http-cache-purge, Ubuntu:26.04:LTS: libnginx-mod-http-cache-purge&lt;/p&gt;
&lt;p&gt;ngx_cache_purge before 3.0.4 can allow file deletion via a symlink attack in certain situations where nginx and a served application (e.g., WordPress) run under the same user account. The attacker must be able to create a symlink inside the cache path. Version 3.0.4 fixes this for the case of a symlink created at an arbitrary earlier time, but does not resolve an applicable TOCTOU race condition. (The ngx_cache_purge module follows symlinks while walking the cache directory tree during purge operations. The module relies on nginx&amp;#39;s ngx_walk_tree(), which relies on stat() and therefore follows symlinks.)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: libnginx-mod-http-cache-purge, Ubuntu:26.04:LTS: libnginx-mod-http-cache-purge&lt;/p&gt;
&lt;p&gt;ngx_cache_purge before 3.0.4 can allow file deletion via a symlink attack in certain situations where nginx and a served application (e.g., WordPress) run under the same user account. The attacker must be able to create a symlink inside the cache path. Version 3.0.4 fixes this for the case of a symlink created at an arbitrary earlier time, but does not resolve an applicable TOCTOU race condition. (The ngx_cache_purge module follows symlinks while walking the cache directory tree during purge operations. The module relies on nginx&amp;#39;s ngx_walk_tree(), which relies on stat() and therefore follows symlinks.)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-108981</guid>
    </item>
  </channel>
</rss>
