babiloo vulnerabilities and fixes
Recent CVEs affecting babiloo, with upgrade or downgrade steps. 1 tracked.
babiloo has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2019-11-12. Highest priority: CVE-2010-3440 (score 29/100).
- CVE-2010-3440 MEDIUM 5.5 UPGRADE MITIGATE babiloo 2.0.9 before 2.0.11 creates temporary files with predictable names when downloading and unpacking dict
FAQ
How do I fix babiloo 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 babiloo being exploited right now?
None of the tracked babiloo CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which babiloo CVE should I patch first?
CVE-2010-3440 currently ranks highest (29/100): babiloo 2.0.9 before 2.0.11 creates temporary files with predictable names when downloading and unpacking dict.