How severe is CVE-2009-2701?

CVE-2009-2701 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2009-2701?

CVE-2009-2701 affects the following packages: zodb3 (PyPI), zodb3 (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2009-2701?

Update zodb3 to 3.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-2701 is resolved across your whole dependency graph.

How do I detect CVE-2009-2701 in my PyPI dependencies?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2009-2701 actively exploited in the wild?

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

CVE-2009-2701 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th 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.

When was CVE-2009-2701 published, and has it been updated?

CVE-2009-2701 was published on May 2, 2022 and was last updated on November 30, 2024. 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

CRITICAL severity

CVE-2009-2701 — zodb3

CRITICAL

CVE-2009-2701 is a critical-severity (CVSS 9.8) vulnerability in zodb3. A fix is available for zodb3 — see the affected versions and patch details below.

Zope Object Database (ZODB) Arbitrary files reading and deletion

Also known asPYSEC-2009-10

Published

May 2, 2022

Updated

Nov 30, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐍zodb3🐍zodb3

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

Unspecified vulnerability in the Zope Enterprise Objects (ZEO) storage-server functionality in Zope Object Database (ZODB) 3.8 before 3.8.3 and 3.9.x before 3.9.0c2, when certain ZEO database sharing and blob support are enabled, allows remote authenticated users to read or delete arbitrary files via unknown vectors.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`zodb3`	≥ 3.8&&< 3.8.3	3.8.3`pip install --upgrade 'zodb3==3.8.3'`
🐍PyPI	`zodb3`	≥ 3.9a0&&< 3.9.0c2	3.9.0c2`pip install --upgrade 'zodb3==3.9.0c2'`

Affected Products

1 product · 11 configurations

Application

zodbzope

11 versions

3.83.8.03.8.13.8.23.9.03.9.0b13.9.0b23.9.0b33.9.0b43.9.0b53.9.0c1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zodb3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zodb3 to 3.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-2701 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2009-2701 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works