# CVE-2026-43891: changedetection.io: Arbitrary Local File Read via crafted backup restore > An attacker can read arbitrary local files by restoring a crafted backup archive containing malicious snapshot paths in changedetection.io. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 May 2026 - **Updated:** 13 May 2026 - **Also known as:** GHSA-8757-69j2-hx56, PYSEC-2026-30 ## What is CVE-2026-43891? CVE-2026-43891 is a high-severity path traversal vulnerability in dgtlmoon changedetection.io, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-73 (External Control of File Name or Path) ## Which versions are affected by CVE-2026-43891? 3 open source packages ship an affected version, including changedetection.io and changedetection-io. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `changedetection.io` | PyPI | All versions | 0.55.1 | | `changedetection-io` | PyPI | All versions | 0.55.1 | | `changedetection-io` | PyPI | All versions | 0.55.1 | Products: Webtechnologies Changedetection. ## How do I fix CVE-2026-43891? Upgrade changedetection.io to 0.55.1 or later. ## Is CVE-2026-43891 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43891 exists. ## Other vulnerabilities in dgtlmoon changedetection.io - [CVE-2026-35490](https://insights.sbomify.com/CVE-2026-35490/): changedetection.io has an Authentication Bypass via Decorator Ordering (critical 9.8) - [CVE-2026-29039](https://insights.sbomify.com/CVE-2026-29039/): changedetection.io: XPath - Arbitrary File Read via unparsed-text() (high 8.8) - [CVE-2026-29065](https://insights.sbomify.com/CVE-2026-29065/): changedetection.io: Zip Slip vulnerability in the backup restore functionality (high 8.8) - [CVE-2026-27696](https://insights.sbomify.com/CVE-2026-27696/): changedetection.io Vulnerable to Server-Side Request Forgery (SSRF) via Watch URLs (high 8.6) - [CVE-2026-33981](https://insights.sbomify.com/CVE-2026-33981/): Changedetection.io Discloses Environment Variables via jq env Builtin in Include Filters (high 8.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-43891 and fix it if it is affected. What it is: CVE-2026-43891 is a high-severity path traversal vulnerability in dgtlmoon changedetection.io, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43891 exists. Affected packages and fixed versions: - changedetection.io (PyPI): affected all versions; fixed in 0.55.1 - changedetection-io (PyPI): affected all versions; fixed in 0.55.1 - changedetection-io (PyPI): affected all versions; fixed in 0.55.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-43891/ (Markdown: https://insights.sbomify.com/CVE-2026-43891/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43891 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43891 - OSV: https://osv.dev/vulnerability/CVE-2026-43891 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-43891/ Summaries are generated and may contain mistakes; the official description above is the record.