CVE-2006-3675

NONECVSS 0.0

0.0

Password Safe 2.11, 2.16 and 3.0BETA1 does not respect the configuration settings for locking the password database when certain dialogue windows are open, which might allow attackers with physical access to obtain the database contents.

CVSS v3: —
EG Score: —
EPSS: 29.9%
KEV: Not listed

Published

July 28, 2006

Last Modified

April 16, 2026

References (12)

cve@mitrehttp://securityreason.com/securityalert/1308
cve@mitrehttp://securitytracker.com/id?1016565
cve@mitrehttp://www.securityfocus.com/archive/1/441040/100/0/threaded
cve@mitrehttp://www.securityfocus.com/bid/19078
cve@mitrehttp://www.symantec.com/enterprise/research/SYMSA-2006-008.txt
cve@mitrehttps://exchange.xforce.ibmcloud.com/vulnerabilities/27933
af854a3a-2127-422b-91ae-364da2661108http://securityreason.com/securityalert/1308
af854a3a-2127-422b-91ae-364da2661108http://securitytracker.com/id?1016565
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/archive/1/441040/100/0/threaded
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/19078
af854a3a-2127-422b-91ae-364da2661108http://www.symantec.com/enterprise/research/SYMSA-2006-008.txt
af854a3a-2127-422b-91ae-364da2661108https://exchange.xforce.ibmcloud.com/vulnerabilities/27933

Data Freshness Timeline

(refreshed 10× in last 7d / 16× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-29 13:40 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:37 UTCepss_batch
2026-05-27 13:37 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-24 16:42 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-21 22:38 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-18 21:29 UTCepss_batch

Frequently asked(4)

What is CVE-2006-3675?

CVE-2006-3675 is a none vulnerability published on July 28, 2006. Password Safe 2.11, 2.16 and 3.0BETA1 does not respect the configuration settings for locking the password database when certain dialogue windows are open, which might allow attackers with physical access to obtain the database contents.

When was CVE-2006-3675 disclosed?

CVE-2006-3675 was first published in the National Vulnerability Database on July 28, 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-3675 actively exploited?

CVE-2006-3675 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2006-3675?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-3675, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2006-3675

Explore →

Is Your Infrastructure Affected by CVE-2006-3675?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2006-3675

📅 Published

🔄 Last Modified

🔗 References (12)