How severe is CVE-2010-3495?

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

Which packages are affected by CVE-2010-3495?

CVE-2010-3495 affects the following packages: zodb3 (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2010-3495?

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

How do I detect CVE-2010-3495 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-2010-3495 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2010-3495 actively exploited in the wild?

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

CVE-2010-3495 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 71th 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-2010-3495?

CVE-2010-3495 is classified as CWE-362 (CWE-362). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2010-3495 published, and has it been updated?

CVE-2010-3495 was published on May 17, 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

CVE-2010-3495 — zodb3

Fix: zopefoundation/ZODB@cfe1627

CVE-2010-3495 is a CWE-362 vulnerability in zodb3. A fix is available for zodb3 — see the affected versions and patch details below.

Zope Object Database Denial of Service vulnerability

Also known asPYSEC-2010-27

Published

May 17, 2022

Updated

Nov 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍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

Race condition in ZEO/StorageServer.py in Zope Object Database (ZODB) before 3.10.0a2 allows remote attackers to cause a denial of service (daemon outage) by establishing and then immediately closing a TCP connection, leading to the accept function having an unexpected return value of None, an unexpected value of None for the address, or an ECONNABORTED, EAGAIN, or EWOULDBLOCK error, a related issue to CVE-2010-3492.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`zodb3`	all versions	3.10.0a2`pip install --upgrade 'zodb3==3.10.0a2'`

Affected Products

1 product · 28 configurations

Application

zodbzope

≤ 3.9.7

27 versions

2.8.112.9.112.10.92.11.43.13.1.13.23.2.43.33.3.33.43.4.1

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.10.0a2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-3495 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Race condition in `ZEO/StorageServer.py` in Zope Object Database (ZODB) before 3.10.0a2 allows remote attackers to cause a denial of service (daemon outage) by establishing and then immediately closing a TCP connection, leading to the accept function having an unexpected return value of None, an unexpected value of None for the address, or an ECONNABORTED, EAGAIN, or EWOULDBLOCK error, a related issue to CVE-2010-3492.

O3 Security · Impact-Aware SCA

Is CVE-2010-3495 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works