py-lmdb project vulnerabilities
Recent CVEs affecting py-lmdb project products. 5 tracked.
py-lmdb project has 5 tracked vulnerabilities, 3 critical. A fixed release or vendor patch exists for 5. Most recent: 2019-09-11. Highest priority: CVE-2019-16227 (score 65/100).
- CVE-2019-16228 HIGH 7.5 UPGRADE An issue was discovered in py-lmdb 0.97
- CVE-2019-16227 CRITICAL 9.8 UPGRADE An issue was discovered in py-lmdb 0.97
- CVE-2019-16226 HIGH 7.5 UPGRADE An issue was discovered in py-lmdb 0.97
- CVE-2019-16225 CRITICAL 9.8 UPGRADE An issue was discovered in py-lmdb 0.97
- CVE-2019-16224 CRITICAL 9.8 UPGRADE An issue was discovered in py-lmdb 0.97
FAQ
How do I fix py-lmdb project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is py-lmdb project being exploited right now?
None of the tracked py-lmdb project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which py-lmdb project CVE should I patch first?
CVE-2019-16227 currently ranks highest (65/100): An issue was discovered in py-lmdb 0.97.