Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

msearch vulnerabilities

Recent CVEs affecting msearch products. 1 tracked.

msearch has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2005-11-21. Highest priority: CVE-2005-2339 (score 30/100).

FAQ

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

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

Which msearch CVE should I patch first?

CVE-2005-2339 currently ranks highest (30/100): Cross-site scripting (XSS) vulnerability in the Unicode version of msearch (unicode-msearch) 1.51(U1)-beta1, 1.

Products

← Back to latest CVEs