Vulnerability Database · npm · gitlabhook · Version
gitlabhook 0.0.1-security
0.0.1-security is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 2 High 0 Medium 0 Low 0 Unrated 0
-
Released 19 Jun 2023
Status latest release
Also known from other sources 2
Newer releases 1
Database updated 22/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
gitlabhook 0.0.1-security vulnerabilities
2 vulnerabilities cover gitlabhook 0.0.1-security. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2019-5485: Command Injection in gitlabhook | 10.0 critical | No fix published | 16 Sep 2019 |
| CVE-2023-476: Malicious code in gitlabhook (npm) | N/A critical | No fix published | 17 Jun 2023 |
Looking for another version, or everything Vulert holds for gitlabhook?
Questions
About gitlabhook 0.0.1-security
Is gitlabhook 0.0.1-security vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover gitlabhook 0.0.1-security: 2 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.0.1-security the latest release of gitlabhook?
Yes. 0.0.1-security is the current release, published 19 Jun 2023. Staying on the current line is what keeps you inside the publisher's fixes.
What does a malicious-package vulnerability mean?
It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.
How do I monitor gitlabhook for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the gitlabhook version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.