Quick answers
- Is CVE-2026-104109 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104109 being exploited in the wild.
- How severe is CVE-2026-104109?
- Medium severity, with a CVSS score of 6.8, published 14 October 2026.
- Which products and versions are affected?
- Error311 FileRise before 3.23.0.
- Is there a fix for CVE-2026-104109?
- Yes: fixed in 3.23.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104109 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104109?
- Check whether you run Error311 FileRise 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.
How to fix
- Fixed in: 3.23.0
Technical details
FileRise extracts archive entries directly to the destination folder before validating the final path resolution. If that destination contains a symlink to a directory outside the storage root, an attacker can place archive entries that traverse through the symlink using ZipArchive::extractTo(), allowing arbitrary file writes or deletions. The vulnerability requires the attacker to either create a pre-existing symlink or leverage one already present in the upload folder, combined with upload or placement of an attacker-controlled ZIP file.
Affected products
- error311 FileRise before 3.23.0
Timeline
- 2026-10-14: disclosed
- 2026-07-25: patched