How severe is CVE-2006-3458?

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

Which packages are affected by CVE-2006-3458?

CVE-2006-3458 affects the following packages: zope2 (PyPI), zope2 (PyPI), zope2 (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2006-3458?

Update zope2 to 2.7.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-3458 is resolved across your whole dependency graph.

How do I detect CVE-2006-3458 in my PyPI dependencies?

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

How do I mitigate CVE-2006-3458 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-2006-3458 actively exploited in the wild?

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

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

CVE-2006-3458 was published on May 1, 2022 and was last updated on November 22, 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-2006-3458 — zope2

CVE-2006-3458 is a security vulnerability in zope2. A fix is available for zope2 — see the affected versions and patch details below.

Zope allows local users to read arbitrary files

Published

May 1, 2022

Updated

Nov 22, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 2, 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 CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

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

Real-World Exposure

3 pkgs affected

🐍zope2🐍zope2🐍zope2

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.7.0 to 2.7.8, 2.8.0 to 2.8.7, and 2.9.0 to 2.9.3 (Zope2) does not disable the "raw" command when providing untrusted users with restructured text (reStructuredText) functionality from docutils, which allows local users to read arbitrary files.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`zope2`	≥ 2.7.0&&< 2.7.8	2.7.8`pip install --upgrade 'zope2==2.7.8'`
🐍PyPI	`zope2`	≥ 2.8.0&&< 2.8.7	2.8.7`pip install --upgrade 'zope2==2.8.7'`
🐍PyPI	`zope2`	≥ 2.9.0&&< 2.9.3	2.9.3`pip install --upgrade 'zope2==2.9.3'`

Affected Products

1 product · 21 configurations

Application

zopezope

21 versions

2.7.02.7.12.7.22.7.32.7.42.7.52.7.62.7.72.7.82.8.02.8.12.8.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zope2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zope2 to 2.7.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-3458 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.

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.

Ubuntu

USN-317-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2006-3458 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works