VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

morgan: vulnerability history, versions and safety

morgan is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 29 releases, from Mar 2019 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 28 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all morgan vulnerabilities

Vulert verdict on morgan 1.12.1 i

Updated on 22 Oct 2026

Good news: 1.12.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 79/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 1.12.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.12.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.12.1 — unaffected i
  • Vulnerabilities on record 4 over 7 years · 3 in the last year i
  • Latest disclosure 28 Sep 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 31,013 packages i
  • Stars 8,200 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for morgan, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.12.1 11 Sep 2026 none MIT — Details →
1.12.0 28 Aug 2026 M1 MIT Yes Details →
1.11.0 02 Jun 2026 M2 MIT Yes Details →
1.10.1 17 Jul 2025 M3 MIT Yes Details →
1.10.0 20 Mar 2020 M3 MIT Yes Details →
1.9.1 11 Sep 2018 M3 MIT Yes Details →
1.9.0 27 Sep 2017 C1 M3 MIT Yes Details →
1.8.2 24 May 2017 C1 M3 MIT Yes Details →
1.8.1 11 Feb 2017 C1 M3 MIT Yes Details →
1.8.0 05 Feb 2017 C1 M3 MIT Yes Details →
1.7.0 19 Feb 2016 C1 M3 MIT Yes Details →
1.6.1 04 Jul 2015 C1 M3 MIT Yes Details →
1.6.0 13 Jun 2015 C1 M3 MIT Yes Details →
1.5.3 11 May 2015 C1 M3 MIT Yes Details →
1.5.2 15 Mar 2015 C1 M3 MIT Yes Details →
1.5.1 31 Dec 2014 C1 M3 MIT Yes Details →
1.5.0 07 Nov 2014 C1 M3 MIT Yes Details →
1.4.1 23 Oct 2014 C1 M3 MIT Yes Details →
1.4.0 17 Oct 2014 C1 M3 MIT Yes Details →
1.3.2 28 Sep 2014 C1 M3 MIT Yes Details →
1.3.1 14 Sep 2014 C1 M3 MIT Yes Details →
1.3.0 02 Sep 2014 C1 M3 MIT Yes Details →
1.2.3 17 Aug 2014 C1 M3 MIT Yes Details →
1.2.2 27 Jul 2014 C1 M3 MIT Yes Details →
1.2.1 26 Jul 2014 C1 M3 MIT Yes Details →
1.2.0 20 Jul 2014 C1 M3 MIT Yes Details →
1.1.1 21 May 2014 C1 M2 MIT Yes Details →
1.1.0 19 May 2014 C1 M2 MIT Yes Details →
1.0.1 05 May 2014 C1 M2 MIT Yes Details →
1.0.0 08 Feb 2014 C1 M2 MIT Yes Details →

All 30 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for morgan

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-5413: Code Injection in morgan 9.8 critical 1.9.1 25 Mar 2019
CVE-2026-5078: Morgan Package Vulnerable to Log Forging via Unneutralized Control Characters 5.3 medium 1.11.0 10 Jul 2026
CVE-2026-15603: Morgan Package Vulnerable to Log Forging via Unescaped Unicode Line Separators 5.3 medium 1.12.0 08 Sep 2026
CVE-2026-87859: Morgan Log Injection Vulnerability via Unescaped Double Quotes 5.3 medium 1.12.1 28 Sep 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 morgan

Is morgan safe to use?

Vulert records 4 vulnerabilities for morgan in npm: 1 critical, 0 high, 3 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is morgan's Vulert package health score?

Vulert scores morgan 79/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of morgan affected?

No. 1.12.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of morgan should I use?

1.12.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does morgan have?

4 vulnerabilities are recorded for morgan in the npm ecosystem: 1 critical, 0 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new morgan vulnerabilities disclosed?

3 vulnerabilities were recorded for morgan in the last 12 months, and the oldest entry in this database dates to 25 Mar 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of morgan are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor morgan for upcoming vulnerabilities?

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