CVE-2006-3675

2.1 LOW 0.5% exploit odds No fix listed

What it is

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.

At a glance

Exploitability: Can be exploited locally on the machine without logging in. Limited direct impact.
Exploit odds: 0.5% chance of exploitation in the next 30 days (EPSS).
Fix: No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

2006-07-28 22:04 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-16 22:27 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.5% in the next 30 days (EPSS).
Severity: 2.1 LOW (CVSS).
Fix: none linked yet, which raises it.

Details

Published: 2006-07-28 22:04 UTC
Last modified: 2026-06-16 22:27 UTC
Exploit probability: 0.5% · EPSS, next 30 days
Record status: Modified

Affected

Counterpane Passwordsafe 2.11
Counterpane Passwordsafe 2.16
Counterpane Passwordsafe 3.0beta1

Attack profile CVSS 2.0 · 2.1

Attack vector: Local
Complexity: Low
Authentication: None
Confidentiality: Partial
Integrity: None
Availability: None

Raw vector

AV:L/AC:L/Au:N/C:P/I:N/A:N

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2006-3675.md and follow it. Check whether this project is affected by CVE-2006-3675. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

References

NVD record · CVE.org record