Ngx Cache Purge
Approved changes feed: RSS · Atom
cpe:2.3:a:denji:ngx_cache_purge:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Denji (2796ca9c-31ed-5ace-85b3-09521d41d872) |
|---|---|
| Product | Ngx Cache Purge (a48a7712-751a-5b71-af9c-f4954a8df553) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-108981 |
vulnerable | 2026-11-03 10:18:02.221603 |
Details available
LOW (3.6)
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.)
Published: 2026-10-12T02:27:15.378Z
Updated: 2026-10-14T17:18:00.208Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.