CVE-2026-25527

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 42% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

changedetection.io is vulnerable to unauthenticated static path traversal

Summary

The /static// route accepts group="..", which causes send_from_directory("static/..", filename) to execute. This moves the base directory up to /app/changedetectionio, enabling unauthenticated local file read of application source files (e.g., flask_app.py). Severity is low information disclosure (C:L).

Details

The vulnerable code is in changedetectionio/flask_app.py inside static_content():

group = re.sub(r'[^\w.-]+', '', group.lower())
filename = re.sub(r'[^\w.-]+', '', filename.lower())
...
return send_from_directory(f"static/{group}", path=filename)

The group sanitization allows dots, so group=".." passes validation. This results in send_from_directory("static/..", filename), effectively shifting the base directory to /app/changedetectionio and allowing reads of files in that directory. The route is unauthenticated, so any user can retrieve source files without logging in.

> Limitation: the route only matches /static// and rejects slashes inside filename, so it cannot traverse further to arbitrary system paths like /etc/passwd. It is limited to files inside the application package directory.

PoC

1) Start an instance (example: Docker on port 5050)
docker run -d --name cdio -p 127.0.0.1:5050:5000 -v cdio-data:/datastore cdio-local

2) Reproduce (URL-encoded traversal)

curl -i http://127.0.0.1:5050/static/%2e%2e/flask_app.py

(curl path passthrough)

curl --path-as-is -i http://127.0.0.1:5050/static/../flask_app.py

3) Observe that the response body contains Python source code from flask_app.py.

Impact

  • Vulnerability type: Directory Traversal / Local File Read
  • Affected users: Anyone with network access (no authentication required)
  • Scope: Source files under /app/changedetectionio
  • Security impact: Internal logic exposure can aid further exploitation (Confidentiality: Low)

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 20, 2026

Vendor Advisories for CVE-2026-25527(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
changedetection-io0.38.2 ... 0.53.1 (180 versions)0.53.2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-11 09:20 UTCEG score recompute
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-09 11:50 UTCEG score recompute
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 22:49 UTCEG score recompute
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-06 11:30 UTCEG score recompute
  11. 2026-09-05 09:23 UTCEG score recompute
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-02 01:03 UTCEG score recompute
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-31 03:02 UTCEG score recompute
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 02:31 UTCEG score recompute
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-28 02:59 UTCEG score recompute
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-27 02:29 UTCEG score recompute
  25. 2026-08-26 14:46 UTCEPSS rescore
Show 62 more
  1. 2026-08-26 01:59 UTCEG score recompute
  2. 2026-08-25 13:48 UTCEPSS rescore
  3. 2026-08-25 01:30 UTCEG score recompute
  4. 2026-08-23 00:25 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:53 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-20 23:23 UTCEG score recompute
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 22:54 UTCEG score recompute
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-18 22:22 UTCEG score recompute
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 21:52 UTCEG score recompute
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 21:19 UTCEG score recompute
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 20:49 UTCEG score recompute
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 20:19 UTCEG score recompute
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 19:20 UTCEG score recompute
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-11 18:49 UTCEG score recompute
  26. 2026-08-11 13:42 UTCEPSS rescore
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-09 17:45 UTCEG score recompute
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-08 17:16 UTCEG score recompute
  31. 2026-08-08 16:37 UTCEPSS rescore
  32. 2026-08-07 16:46 UTCEG score recompute
  33. 2026-08-06 16:16 UTCEG score recompute
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-04 15:16 UTCEG score recompute
  37. 2026-08-04 15:10 UTCEPSS rescore
  38. 2026-08-03 14:47 UTCEG score recompute
  39. 2026-08-03 10:36 UTCEPSS rescore
  40. 2026-08-02 14:18 UTCEG score recompute
  41. 2026-08-02 02:26 UTCEPSS rescore
  42. 2026-08-01 13:48 UTCEG score recompute
  43. 2026-08-01 04:16 UTCEPSS rescore
  44. 2026-07-31 13:19 UTCEG score recompute
  45. 2026-07-30 16:27 UTCEPSS rescore
  46. 2026-07-30 12:49 UTCEG score recompute
  47. 2026-07-30 01:30 UTCEPSS rescore
  48. 2026-07-29 12:18 UTCEG score recompute
  49. 2026-07-28 15:36 UTCEPSS rescore
  50. 2026-07-28 11:48 UTCEG score recompute
  51. 2026-07-26 10:46 UTCEG score recompute
  52. 2026-07-25 14:18 UTCEPSS rescore
  53. 2026-07-25 14:17 UTCEPSS rescore
  54. 2026-07-24 14:17 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 14:18 UTCEPSS rescore
  57. 2026-07-23 03:07 UTCEG score recompute
  58. 2026-07-22 14:08 UTCEPSS rescore
  59. 2026-07-21 15:24 UTCEPSS rescore
  60. 2026-07-21 15:24 UTCEPSS rescore
  61. 2026-07-20 19:32 UTCEG score recompute
  62. 2026-07-20 19:32 UTCOSV refresh

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-25527.yaml
    First seen Jan 1, 2026

    changedetection.io <= 0.52.9 - Unauthenticated Path Traversal

    Open source ↗

Frequently asked(5)

What is CVE-2026-25527?
CVE-2026-25527 is a medium vulnerability published on July 20, 2026. changedetection.io is vulnerable to unauthenticated static path traversal Summary The /static/<group>/<filename> route accepts group="..", which causes sendfromdirectory("static/..", filename) to execute. This moves the base directory up to /app/changedetectionio, enabling unauthenticated local…
When was CVE-2026-25527 disclosed?
CVE-2026-25527 was first published in the National Vulnerability Database on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25527 actively exploited?
CVE-2026-25527 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 41.8% of all scored CVEs.
What is the CVSS score of CVE-2026-25527?
CVE-2026-25527 has a CVSS v4.0 base score of 5.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-25527?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25527, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25527

Explore →

Is Your Infrastructure Affected by CVE-2026-25527?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.