Quick answers
- Is CVE-2026-84441 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84441 being exploited in the wild.
- How severe is CVE-2026-84441?
- High severity, with a CVSS score of 7.3, published 2 September 2026.
- Which products and versions are affected?
- Piwigo up to 16.3.0.
- Is there a fix for CVE-2026-84441?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-84441 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-84441?
- Check whether you run Piwigo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a path traversal flaw in Piwigo's image derivative handler (i.php), which processes and caches resized/transformed image versions. The component fails to properly validate and sanitize file path inputs when constructing derivative image locations, allowing an unauthenticated remote attacker to craft malicious URLs that traverse the directory structure. By manipulating path parameters and using valid derivative suffixes, an attacker can write derivative images to arbitrary locations within the _data directory and potentially beyond, such as theme or plugin directories. No authentication is required, and the attack is network-accessible. Successful exploitation could lead to arbitrary file writes, code injection, or complete compromise of the gallery installation.
Affected products
- Piwigo Piwigo up to 16.3.0
Timeline
- 2026-09-02: disclosed
- other: Proof of concept publicly available on GitHub