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.)
References
Configurations
No configuration.
History
12 Oct 2026, 03:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-12 03:17
Updated : 2026-10-16 19:56
NVD link : CVE-2026-108981
Mitre link : CVE-2026-108981
CVE.ORG link : CVE-2026-108981
JSON object : View
Products Affected
No product.
CWE
CWE-61
UNIX Symbolic Link (Symlink) Following
