CVE-2014-1921: parcimonie before 0.8.1, when using a large keyring, sleeps for the same amount of time between fetches, which
CVE-2014-1921 is a high-severity flaw (CVSS 7.5) affecting parcimonie. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
parcimonie before 0.8.1, when using a large keyring, sleeps for the same amount of time between fetches, which allows attackers to correlate key fetches via unspecified vectors.
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| EPSS exploit chance | 1.6% (top 25%) |
| CISA exploited list | No |
| Weakness | CWE-362 |
| Published | 2014-02-14 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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-2014-1921?
parcimonie: upgrade to newer than 0.7.1-1. Exact commands for each OS are on this page.
Is CVE-2014-1921 being exploited?
CVE-2014-1921 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-2014-1921 affect?
CVE-2014-1921 affects parcimonie. Severity is high (CVSS 7.5). parcimonie before 0.8.1, when using a large keyring, sleeps for the same amount of time between fetches, which allows attackers to correlate key fetches via unspecified vectors.
How urgent is CVE-2014-1921?
Priority 45/100. High severity