Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

gitlabhook vulnerabilities and fixes

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

gitlabhook has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2019-09-13. Highest priority: CVE-2019-5485 (score 70/100).

FAQ

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

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

Which gitlabhook CVE should I patch first?

CVE-2019-5485 currently ranks highest (70/100): NPM package gitlabhook version 0.0.17 is vulnerable to a Command Injection vulnerability.

← Back to latest CVEs