How severe is CVE-2002-0170?

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

Which packages are affected by CVE-2002-0170?

CVE-2002-0170 affects the following packages: zope (PyPI), zope (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2002-0170?

Update zope to 2.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2002-0170 is resolved across your whole dependency graph.

How do I detect CVE-2002-0170 in my PyPI dependencies?

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

How do I mitigate CVE-2002-0170 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.

How does O3 Security protect against CVE-2002-0170?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2002-0170 can be triaged on real exposure rather than presence alone.

Is CVE-2002-0170 actively exploited in the wild?

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

CVE-2002-0170 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 74th 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-2002-0170 published, and has it been updated?

CVE-2002-0170 was published on April 30, 2022 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-2002-0170 — zope

CVE-2002-0170 is a security vulnerability in zope. A fix is available for zope — see the affected versions and patch details below.

Zope does not properly verify the access for objects with proxy roles

Also known asPYSEC-2026-758

Published

Apr 30, 2022

Updated

Jul 6, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

🐍zope🐍zope

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

Zope 2.2.0 through 2.5.1 does not properly verify the access for objects with proxy roles, which could allow some users to access documents in violation of the intended configuration.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`zope`	≥ 2.2.0&&< 2.4.4	2.4.4`pip install --upgrade 'zope==2.4.4'`
🐍PyPI	`zope`	≥ 2.5.0&&< 2.5.1	2.5.1`pip install --upgrade 'zope==2.5.1'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zope, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zope to 2.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2002-0170 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2002-0170 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2002-0170. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red Hat

RHSA-2002:060Red Hat Powertools 7.0

Frequently Asked Questions

Zope 2.2.0 through 2.5.1 does not properly verify the access for objects with proxy roles, which could allow some users to access documents in violation of the intended configuration.

O3 Security · Impact-Aware SCA

Is CVE-2002-0170 in your dependencies?

O3 Security finds CVE-2002-0170 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works