CVE-2019-5485: NPM package gitlabhook version 0.0.17 is vulnerable to a Command Injection vulnerability

Q: How do I fix CVE-2019-5485?

gitlabhook: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2019-5485 being exploited?

CVE-2019-5485 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-5485 affect?

CVE-2019-5485 affects gitlabhook. Severity is critical (CVSS 10.0). NPM package gitlabhook version 0.0.17 is vulnerable to a Command Injection vulnerability. Arbitrary commands can be injected through the repository name.

Q: How urgent is CVE-2019-5485?

Priority 70/100. Critical severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 10.0REMOTEDOWNGRADE

CVE-2019-5485 is a critical-severity flaw (CVSS 10.0) affecting gitlabhook. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

NPM package gitlabhook version 0.0.17 is vulnerable to a Command Injection vulnerability. Arbitrary commands can be injected through the repository name.

Why this priority

Critical severity
EPSS top 1%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	10.0 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	58.8% (top 1%)
CISA exploited list	No
Weakness	CWE-78
Published	2019-09-13
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: gitlabhook project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-09-13 18:15 UTCPublished CVE record published
2026-06-17 02:37 UTCUpdated Record last modified

gitlabhook project gitlabhook DOWNGRADE

Affected: 0.0.17

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.0.17

1. Check installed version

npm ls gitlabhook

2. No fixed release: DOWNGRADE to a release before 0.0.17

npm view gitlabhook versions npm install gitlabhook@"<0.0.17"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.

npm · gitlabhook · NO FIX YET · vulnerable: <= 0.0.17 · source

Fedora 46 · nodejs-pnpm12 · FIXED · 12.17.0-1.fc46 · FEDORA-2026-7adfb2bcdd · source

sudo dnf upgrade --advisory=FEDORA-2026-7adfb2bcdd

Fedora ELN · wget2 · FIXED · 2.3.0-3.eln159 · FEDORA-2026-811b4922a5 · source

sudo dnf upgrade --advisory=FEDORA-2026-811b4922a5

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Write-up: hackerone.com/reports/685447
Exploit-DB: NPMJS gitlabhook 0.0.17 - 'repository' Remote Command Execution

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-5485?

gitlabhook: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-5485 being exploited?

CVE-2019-5485 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-5485 affect?

CVE-2019-5485 affects gitlabhook. Severity is critical (CVSS 10.0). NPM package gitlabhook version 0.0.17 is vulnerable to a Command Injection vulnerability. Arbitrary commands can be injected through the repository name.

How urgent is CVE-2019-5485?

Priority 70/100. Critical severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

npm packages vulnerabilities

References

← Back to latest CVEs