Quick answers
- Is CVE-2026-95273 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95273 being exploited in the wild.
- How severe is CVE-2026-95273?
- Medium severity, with a CVSS score of 4.3, published 22 September 2026.
- Which products and versions are affected?
- Dgtlmoon Changedetection.Io up to 0.60.7.
- Is there a fix for CVE-2026-95273?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-95273 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-95273?
- Check whether you run Dgtlmoon Changedetection.Io 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.
Technical details
The static_content() function in changedetectionio/flask_app.py fails to sanitize the filename route parameter before passing it to os.path.join() to construct a directory path. When group=visual_selector_data, an attacker can inject path traversal sequences (../) to escape the datastore directory and read elements.deflate files from other watches or system directories. The vulnerability violates Werkzeug's send_from_directory contract which explicitly warns the directory parameter must not be client-supplied.
Affected products
- dgtlmoon changedetection.io up to 0.60.7
Timeline
- 2026-09-22: disclosed: Publicly disclosed vulnerability
- 2026: other: Vendor contacted early but did not respond