https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T16:08:10.070120+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-318018 EUVD-2026-318018 2026-10-02T16:08:10.073415+00:00 EUVD-2026-318018 https://cve.radiocsirt.org/vuln/fkie_cve-2026-43891 fkie_cve-2026-43891 2026-10-02T16:08:10.073454+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-8757-69j2-hx56 GHSA-8757-69j2-hx56 — changedetection.io has an Arbitrary Local File Read via a crafted backup restore 2026-10-02T16:08:10.073500+00:00

Affected: PyPI: changedetection.io

### Details 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`.

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)

After restore, the application parses `history.txt` in the watch `history` property. This is the core trust-boundary issue.

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)

The relevant logic is effectively:

```python if os.sep not in v and '/' not in v and '\\' not in v: v = os.path.join(self.data_dir, v) el…

 https://cve.radiocsirt.org/vuln/pysec-2026-30 PYSEC-2026-30 2026-10-02T16:08:10.073613+00:00

Affected: PyPI: changedetection-io

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.