How severe is CVE-2006-3695?

CVE-2006-3695 has a CVSS score of 9.4/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2006-3695?

CVE-2006-3695 affects the following packages: trac (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2006-3695?

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

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

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

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

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2006-3695 actively exploited in the wild?

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

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

CVE-2006-3695 was published on July 21, 2006 and was last updated on April 10, 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

CRITICAL severity

CVE-2006-3695 — trac

CRITICAL

CVE-2006-3695 is a critical-severity (CVSS 9.4) vulnerability in trac. A fix is available for trac — see the affected versions and patch details below.

Trac reStructuredText breach of privacy and denial of service vulnerability

Also known asGHSA-r524-c2gf-5chrPYSEC-2006-2

Published

Jul 21, 2006

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% 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

1 pkg affected

🐍trac

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

Trac before 0.9.6 does not disable the "raw" or "include" commands when providing untrusted users with restructured text (reStructuredText) functionality from docutils, which allows remote attackers to read arbitrary files, perform cross-site scripting (XSS) attacks, or cause a denial of service via unspecified vectors. NOTE: this might be related to CVE-2006-3458.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

tracedgewall_software

≤ 0.9.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trac, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update trac to 0.9.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-3695 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2006-3695 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jul 21, 2006

Last updated

Apr 10, 2026

Identifiers

CVE-2006-3695

GHSA-r524-c2gf-5chr

PYSEC-2006-2

References

Advisorysecunia.com Advisorysecunia.com Advisorydebian.org · dsa 1152 Advisoryvupen.com Advisorynvd.nist.gov · CVE 2006 3695 Websecuritytracker.com · id Webtrac.edgewall.org · ChangeLog Websecurityfocus.com Webexchange.xforce.ibmcloud.com Webexchange.xforce.ibmcloud.com Webgithub.com · PYSEC 2006 2.yaml Webweb.archive.org · ChangeLog Webweb.archive.org Webweb.archive.org Webweb.archive.org

Related vulnerabilities

This CVE is critical severity — higher than any of the other 7 CVEs affecting trac (highest there: high).

CVE-2009-4405CVE-2006-5878CVE-2005-4644CVE-2007-1406CVE-2008-2951CVE-2007-1405CVE-2008-3328

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 10, 2026