CVE-2006-3675: Password Safe 2.11, 2.16 and 3.0BETA1 does not respect the configuration settings for locking the password dat

Routine

LOW 2.1DOWNGRADE

CVE-2006-3675 is a low-severity flaw (CVSS 2.1) affecting passwordsafe. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	2.1 (Low)
EPSS exploit chance	0.5% (top 61%)
CISA exploited list	No
Published	2006-07-28
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: counterpane

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2006-07-28 22:04 UTCPublished CVE record published
2026-06-16 22:27 UTCUpdated Record last modified

counterpane passwordsafe DOWNGRADE

Affected: 2.11 · 2.16 · 3.0beta1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.11

1. Check installed version

apt-cache policy passwordsafe || rpm -q passwordsafe || passwordsafe --version

2. No fixed release: DOWNGRADE to a release before 2.11 (Debian / Ubuntu)

apt-cache madison passwordsafe sudo apt install passwordsafe=<VERSION_BEFORE_2.11> sudo apt-mark hold passwordsafe

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list passwordsafe sudo dnf downgrade passwordsafe-<VERSION_BEFORE_2.11> sudo dnf versionlock add passwordsafe

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2006-3675?

passwordsafe: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2006-3675 being exploited?

CVE-2006-3675 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2006-3675 affect?

CVE-2006-3675 affects passwordsafe. Severity is low (CVSS 2.1). 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.

How urgent is CVE-2006-3675?

Priority 22/100. Public exploit reference

Software pages

Windows vulnerabilities

Related CVEs

CVE-2005-3801 MEDIUM 4.6 DOWNGRADE CounterPane PasswordSafe 1.x and 2.x allows local users to test possible encryption keys against a subset of t

References

← Back to latest CVEs