Tor before 0.1.1.20 does not validate that a server descriptor's fingerprint line matches its identity key, which allows remote attackers to spoof the fingerprint line, which might be trusted by users or other applications.
CVE-2006-3418
NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 2%CVSS: —Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- —
- EG Score
- 0.0(none)
- EPSS
- 79.5%
- KEV
- Not listed
Published
July 7, 2006
Last Modified
April 16, 2026
References (8)
- cve@mitrehttp://secunia.com/advisories/20514
- cve@mitrehttp://security.gentoo.org/glsa/glsa-200606-04.xml
- cve@mitrehttp://tor.eff.org/cvs/tor/ChangeLog
- cve@mitrehttp://www.osvdb.org/25881
- af854a3a-2127-422b-91ae-364da2661108http://secunia.com/advisories/20514
- af854a3a-2127-422b-91ae-364da2661108http://security.gentoo.org/glsa/glsa-200606-04.xml
- af854a3a-2127-422b-91ae-364da2661108http://tor.eff.org/cvs/tor/ChangeLog
- af854a3a-2127-422b-91ae-364da2661108http://www.osvdb.org/25881
Frequently asked(4)
What is CVE-2006-3418?
CVE-2006-3418 is a none vulnerability published on July 7, 2006. Tor before 0.1.1.20 does not validate that a server descriptor's fingerprint line matches its identity key, which allows remote attackers to spoof the fingerprint line, which might be trusted by users or other applications.
When was CVE-2006-3418 disclosed?
CVE-2006-3418 was first published in the National Vulnerability Database on July 7, 2006, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-3418 actively exploited?
CVE-2006-3418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 79.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2006-3418?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-3418, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2006-3418
Is Your Infrastructure Affected by CVE-2006-3418?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.