Symlink Following Affecting libnginx-mod-http-cache-purge package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-LIBNGINXMODHTTPCACHEPURGE-20840224
- published12 Oct 2026
- disclosed12 Oct 2026
Introduced: 12 Oct 2026
NewCVE-2026-108981 (opens in a new tab)How to fix?
There is no fixed version for Echo:latest libnginx-mod-http-cache-purge.
NVD Description
Note: Versions mentioned in the description apply only to the upstream libnginx-mod-http-cache-purge package and not the libnginx-mod-http-cache-purge package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
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's ngx_walk_tree(), which relies on stat() and therefore follows symlinks.)