← Back
CVE-2026-25527
Path Traversal in changedetection.io (CVE-2026-25527)
Summary
path traversal in changedetection.io (CVE-2026-25527). Risk of unauthorized operations or information disclosure. Exploitable via ``flask_app.py``. Mitigation: upgrade to `0.53.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-25527** has been found in changedetection.io.
Attackers can target a specific entry point like ``flask_app.py`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade changedetection.io to **0.53.2** or later.
If unsure, ask your IT team or search "changedetection.io CVE-2026-25527" on the vendor's site.
CVE-2026-25527 (changedetection.io) — CWE-22 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `flask_app.py`
Patched: `0.53.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in changedetection.io. Attackers reach the vulnerable code path via ``flask_app.py`` without authentication.
📍 Affected scope
changedetection.io — . Attack surface: `flask_app.py`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.53.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'changedetection.io' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'changedetection.io' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `changedetection.io` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade changedetection.io to 0.53.2ステージング環境で 0.53.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
changedetection.io
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.53.2"}]}]
PyPI
changedetection-io
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.53.2"}]}]
References
- patch https://github.com/dgtlmoon/changedetection.io/commit/9d38b4517364831889b5b0d7b3465fd060403fd4
- report https://github.com/dgtlmoon/changedetection.io/security/advisories/GHSA-9jj8-v89v-xjvw
- web https://nvd.nist.gov/vuln/detail/CVE-2026-25527
- web https://github.com/pypa/advisory-database/tree/main/vulns/changedetection-io/PYSEC-2026-2124.yaml
- web https://github.com/advisories/GHSA-9jj8-v89v-xjvw