Vulnerability Database · npm · gitlog · Version

gitlog 3.3.6

3.3.6 is affected by 1 vulnerability.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 5.1.0.

Critical 1 High 0 Medium 0 Low 0 Unrated 0

All gitlog versions & vulnerabilities → Source repository Search the database for this package →

Released 09 Apr 2020 Licence BSD-3-Clause Also known from other sources 1 Newer releases 35 Database updated 23/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.

Scan your app free →

01 Vulnerabilities affecting this version

gitlog 3.3.6 vulnerabilities

1 vulnerability cover gitlog 3.3.6. Open the full list in the database.

Vulnerability	Severity	Fixed version	Disclosed
CVE-2021-26541: Command injection in gitlog	9.8 critical	4.0.4	13 Apr 2021

Looking for another version, or everything Vulert holds for gitlog?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram

Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.

Join the channel →

Questions

About gitlog 3.3.6

Is gitlog 3.3.6 vulnerable?

Yes. 1 vulnerability in the Vulert database cover gitlog 3.3.6: 1 critical, 0 high, 0 medium and 0 low. The upgrade Vulert recommends is 5.1.0, and each entry above names the fixed version to move to.

Which version of gitlog should I use instead of 3.3.6?

5.1.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 3.3.6 the latest release of gitlog?

No. 3.3.6 was published 09 Apr 2020, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor gitlog for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the gitlog version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.