CVE-2001-0435
The split key mechanism used by PGP 7.0 allows a key share holder to obtain access to the entire...
The split key mechanism used by PGP 7.0 allows a key share holder to obtain access to the entire key by setting the "Cache passphrase while logged on" option and capturing the passphrases of other share holders as they authenticate.
Exploit likelihood
What each source reports
NVD Score used
4.6
The split key mechanism used by PGP 7.0 allows a key share holder to obtain access to the entire key by setting the "Cache passphrase while logged on" option and capturing the passphrases of other share holders as they authenticate.
- Record
CVE-2001-0435- CVSS 2.0
- 4.6 Medium
AV:L/AC:L/Au:N/C:P/I:P/A:P - Updated
- 2026-11-02
CVE List No score
The split key mechanism used by PGP 7.0 allows a key share holder to obtain access to the entire key by setting the "Cache passphrase while logged on" option and capturing the passphrases of other share holders as they authenticate.
- Record
CVE-2001-0435- Updated
- 2026-11-02
EUVDEUVD-2001-0432 No score
The split key mechanism used by PGP 7.0 allows a key share holder to obtain access to the entire key by setting the "Cache passphrase while logged on" option and capturing the passphrases of other share holders as they authenticate.
- Record
EUVD-2001-0432- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-5rmq-q5qg-vcf7 No score
The split key mechanism used by PGP 7.0 allows a key share holder to obtain access to the entire...
The split key mechanism used by PGP 7.0 allows a key share holder to obtain access to the entire key by setting the "Cache passphrase while logged on" option and capturing the passphrases of other share holders as they authenticate.
- Record
GHSA-5rmq-q5qg-vcf7- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2001-0435 is a medium vulnerability (CVSS 4.6) in Pgp, published May 24, 2001. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.33%, the 26th percentile. No source names a fixed version.