https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 22:03:31 +0000 https://cve.radiocsirt.org/vuln/cve-2026-43891 <p><strong>Affected:</strong> dgtlmoon changedetection.io</p> <p>changedetection.io is a free open source web page change detection tool. Prior to 0.55.1, the vulnerability is caused by trusting attacker-controlled snapshot paths restored from backup files. The vulnerable flow starts in the backup restore logic. When a backup ZIP is restored, the application extracts the archive and copies each restored watch UUID directory directly into the live datastore using shutil.copytree(entry.path, dst_dir). This preserves attacker-controlled files inside the restored watch directory, including history.txt. After restore, the application parses history.txt in the watch history property and returns the contents of the targeted local file. This vulnerability is fixed in 0.55.1.</p> <p><strong>Affected:</strong> dgtlmoon changedetection.io</p> <p>changedetection.io is a free open source web page change detection tool. Prior to 0.55.1, the vulnerability is caused by trusting attacker-controlled snapshot paths restored from backup files. The vulnerable flow starts in the backup restore logic. When a backup ZIP is restored, the application extracts the archive and copies each restored watch UUID directory directly into the live datastore using shutil.copytree(entry.path, dst_dir). This preserves attacker-controlled files inside the restored watch directory, including history.txt. After restore, the application parses history.txt in the watch history property and returns the contents of the targeted local file. This vulnerability is fixed in 0.55.1.</p> https://cve.radiocsirt.org/vuln/cve-2026-43891 https://cve.radiocsirt.org/vuln/ghsa-8757-69j2-hx56 <p><strong>Affected:</strong> PyPI: changedetection.io</p> <p>### Details The vulnerability is caused by trusting attacker-controlled snapshot paths restored from backup files.</p> <p>The vulnerable flow starts in the backup restore logic. When a backup ZIP is restored, the application extracts the archive and copies each restored watch UUID directory directly into the live datastore using `shutil.copytree(entry.path, dst_dir)`. This preserves attacker-controlled files inside the restored watch directory, including `history.txt`.</p> <p>Relevant code: - [changedetectionio/blueprint/backups/restore.py](https://github.com/dgtlmoon/changedetection.io/blob/master/changedetectionio/blueprint/backups/restore.py#L132) - [changedetectionio/blueprint/backups/restore.py](https://github.com/dgtlmoon/changedetection.io/blob/master/changedetectionio/blueprint/backups/restore.py#L141)</p> <p>After restore, the application parses `history.txt` in the watch `history` property. This is the core trust-boundary issue.</p> <p>Relevant code: - [changedetectionio/model/Watch.py](https://github.com/dgtlmoon/changedetection.io/blob/master/changedetectionio/model/Watch.py#L460) - [changedetectionio/model/Watch.py](https://github.com/dgtlmoon/changedetection.io/blob/master/changedetectionio/model/Watch.py#L471) - [changedetectionio/model/Watch.py](https://github.com/dgtlmoon/changedetection.io/blob/master/changedetectionio/model/Watch.py#L478)</p> <p>The relevant logic is effectively:</p> <p>```python if os.sep not in v and &#39;/&#39; not in v and &#39;\\&#39; not in v: v = os.path.join(self.data_dir, v) el…</p> <p><strong>Affected:</strong> PyPI: changedetection.io</p> <p>### Details The vulnerability is caused by trusting attacker-controlled snapshot paths restored from backup files.</p> <p>The vulnerable flow starts in the backup restore logic. When a backup ZIP is restored, the application extracts the archive and copies each restored watch UUID directory directly into the live datastore using `shutil.copytree(entry.path, dst_dir)`. This preserves attacker-controlled files inside the restored watch directory, including `history.txt`.</p> <p>Relevant code: - [changedetectionio/blueprint/backups/restore.py](https://github.com/dgtlmoon/changedetection.io/blob/master/changedetectionio/blueprint/backups/restore.py#L132) - [changedetectionio/blueprint/backups/restore.py](https://github.com/dgtlmoon/changedetection.io/blob/master/changedetectionio/blueprint/backups/restore.py#L141)</p> <p>After restore, the application parses `history.txt` in the watch `history` property. This is the core trust-boundary issue.</p> <p>Relevant code: - [changedetectionio/model/Watch.py](https://github.com/dgtlmoon/changedetection.io/blob/master/changedetectionio/model/Watch.py#L460) - [changedetectionio/model/Watch.py](https://github.com/dgtlmoon/changedetection.io/blob/master/changedetectionio/model/Watch.py#L471) - [changedetectionio/model/Watch.py](https://github.com/dgtlmoon/changedetection.io/blob/master/changedetectionio/model/Watch.py#L478)</p> <p>The relevant logic is effectively:</p> <p>```python if os.sep not in v and &#39;/&#39; not in v and &#39;\\&#39; not in v: v = os.path.join(self.data_dir, v) el…</p> https://cve.radiocsirt.org/vuln/ghsa-8757-69j2-hx56