Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

berkeley vulnerabilities

Recent CVEs affecting berkeley products. 1 tracked.

berkeley has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2009-01-15. Highest priority: CVE-2009-0126 (score 44/100).

FAQ

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

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

Which berkeley CVE should I patch first?

CVE-2009-0126 currently ranks highest (44/100): The decrypt_public function in lib/crypt.cpp in the client in Berkeley Open Infrastructure for Network Computi.

Products

← Back to latest CVEs