changedetection.io hat eine Zip Slip Schwachstelle in der Backup-Wiederherstellungsfunktionalität

The Zip Slip vulnerability in changedetection-io poses a significant risk because it allows for arbitrary file overwrites. An attacker could upload a specially crafted ZIP archive containing path traversal sequences (e.g., ../) to escape the intended extraction directory. This could lead to the modification or deletion of critical system files, configuration files, or even application code. Successful exploitation could result in complete system compromise, data loss, or denial of service. The impact is amplified if the application runs with elevated privileges, allowing the attacker to overwrite files in protected areas of the filesystem. This vulnerability shares similarities with other Zip Slip vulnerabilities where inadequate path validation during ZIP archive extraction leads to unintended file modifications.

Systems running changedetection-io versions prior to 0.54.4 are at risk. This includes users who have not applied security updates and those who rely on the backup and restore functionality for data protection. Shared hosting environments where multiple users share the same server instance are particularly vulnerable, as a compromised user could potentially exploit this vulnerability to affect other users.

• python / server:

find / -name 'changedetection-io' -type d -exec grep -i 'zipfile.ZipFile' {}/ -H 2>/dev/null | grep -i 'extractall' 

• generic web:

curl -I <changedetection-io_url>/restore_backup.php # Check for endpoint exposure

1. 2026-03-04Disclosure

   disclosure

1. Reserviert2026-03-03
2. Veröffentlicht2026-03-04
3. Geändert2026-03-06
4. EPSS aktualisiert2026-03-23

The primary mitigation for CVE-2026-29065 is to upgrade changedetection-io to version 0.54.4 or later, which includes the necessary path validation fixes. If upgrading immediately is not feasible, consider implementing temporary workarounds. One approach is to restrict the types of files that can be uploaded and stored as backups. Another is to implement strict file permissions on the backup directory to limit the impact of a potential file overwrite. Additionally, monitor the application's logs for any suspicious file access or modification attempts. After upgrading, verify the fix by attempting a backup restore with a ZIP archive containing path traversal sequences to ensure that the files are not overwritten.