Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

baglamukhi vulnerabilities and fixes

Recent CVEs affecting baglamukhi, with upgrade or downgrade steps. 1 tracked.

baglamukhi has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2014-09-23. Highest priority: CVE-2014-6666 (score 24/100).

FAQ

How do I fix baglamukhi 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 baglamukhi being exploited right now?

None of the tracked baglamukhi CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which baglamukhi CVE should I patch first?

CVE-2014-6666 currently ranks highest (24/100): The Baglamukhi (aka com.wshribaglamukhiblog) application 0.1 for Android does not verify X.509 certificates fr.

← Back to latest CVEs