How severe is CVE-2007-5201?

No CVSS score has been assigned to CVE-2007-5201 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2007-5201?

CVE-2007-5201 affects the following packages: duplicity (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2007-5201?

Update duplicity to 0.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-5201 is resolved across your whole dependency graph.

How do I detect CVE-2007-5201 in my PyPI dependencies?

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

How do I mitigate CVE-2007-5201 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2007-5201 actively exploited in the wild?

No public exploit code has been indexed for CVE-2007-5201 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 CVE-2007-5201?

CVE-2007-5201 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th 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 CVE-2007-5201?

CVE-2007-5201 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2007-5201 published, and has it been updated?

CVE-2007-5201 was published on October 4, 2007 and was last updated on July 6, 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

CVE-2007-5201 — duplicity

CVE-2007-5201 is a Information Exposure vulnerability in duplicity. A fix is available for duplicity — see the affected versions and patch details below.

FTP backend for Duplicity Discloses Passwords to Process Listing

Also known asGHSA-wxcw-rqxc-hj85PYSEC-2026-633

Published

Oct 4, 2007

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍duplicity

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

The FTP backend for Duplicity before 0.4.9 sends the password as a command line argument when calling ncftp, which might allow local users to read the password by listing the process and its arguments.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`duplicity`	all versions	0.4.9`pip install --upgrade 'duplicity==0.4.9'`

Affected Products

1 product · 1 configurations

Application

duplicityduplicity_project

< 0.4.9

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for duplicity, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update duplicity to 0.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-5201 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2007-5201 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works