VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

marked: vulnerability history, versions and safety

marked is a package in the npm ecosystem. Vulert records 18 vulnerabilities for it across 2 releases, from Oct 2017 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
18 vulnerabilities recorded H5 M12 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 29 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all marked vulnerabilities

Vulert verdict on marked 18.1.1 i

Updated on 23 Oct 2026

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

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 18.1.1 — unaffected i
  • Vulnerabilities on record 18 over 8 years · 1 in the last year i
  • Latest disclosure 29 Apr 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 4,586 packages i
  • Stars 37,242 i
  • OpenSSF scorecard 5/10 i
  • Last release this month 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 marked, 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
18.1.1 12 Oct 2026 none MIT — Details →
18.1.0 05 Oct 2026 none MIT — Details →
18.0.14 22 Sep 2026 none MIT — Details →
18.0.13 12 Sep 2026 none MIT — Details →
18.0.12 07 Sep 2026 none MIT — Details →
18.0.11 24 Aug 2026 none MIT — Details →
18.0.10 18 Aug 2026 none MIT — Details →
18.0.9 04 Aug 2026 none MIT — Details →
18.0.8 04 Aug 2026 none MIT — Details →
18.0.7 21 Jul 2026 none MIT — Details →
18.0.6 09 Jul 2026 none MIT — Details →
18.0.5 04 Jun 2026 none MIT — Details →
18.0.4 19 May 2026 none MIT — Details →
18.0.3 01 May 2026 none MIT — Details →
18.0.2 18 Apr 2026 none MIT — Details →
18.0.1 17 Apr 2026 H1 MIT Yes Details →
18.0.0 07 Apr 2026 H1 MIT Yes Details →
17.0.6 05 Apr 2026 none MIT — Details →
17.0.5 20 Mar 2026 none MIT — Details →
17.0.4 04 Mar 2026 none MIT — Details →
17.0.3 17 Feb 2026 none MIT — Details →
17.0.2 11 Feb 2026 none MIT — Details →
17.0.1 20 Nov 2025 none MIT — Details →
17.0.0 07 Nov 2025 none MIT — Details →
16.4.2 06 Nov 2025 none MIT — Details →
16.4.1 17 Oct 2025 none MIT — Details →
16.4.0 07 Oct 2025 none MIT — Details →
16.3.0 14 Sep 2025 none MIT — Details →
16.2.1 27 Aug 2025 none MIT — Details →
16.2.0 18 Aug 2025 none MIT — Details →
16.1.2 04 Aug 2025 none MIT — Details →
16.1.1 18 Jul 2025 none MIT — Details →
16.1.0 17 Jul 2025 none MIT — Details →
16.0.0 27 Jun 2025 none MIT — Details →
15.0.12 20 May 2025 none MIT — Details →
15.0.11 25 Apr 2025 none MIT — Details →
15.0.10 23 Apr 2025 none MIT — Details →
15.0.9 21 Apr 2025 none MIT — Details →
15.0.8 07 Apr 2025 none MIT — Details →
15.0.7 10 Feb 2025 none MIT — Details →
15.0.6 06 Jan 2025 none MIT — Details →
15.0.5 02 Jan 2025 none MIT — Details →
15.0.4 15 Dec 2024 none MIT — Details →
15.0.3 29 Nov 2024 none MIT — Details →
15.0.2 20 Nov 2024 none MIT — Details →
15.0.1 18 Nov 2024 none MIT — Details →
15.0.0 09 Nov 2024 none MIT — Details →
14.1.4 07 Nov 2024 none MIT — Details →
14.1.3 15 Oct 2024 none MIT — Details →
14.1.2 08 Sep 2024 none MIT — Details →
14.1.1 04 Sep 2024 none MIT — Details →
14.1.0 26 Aug 2024 none MIT — Details →
14.0.0 07 Aug 2024 none MIT — Details →
13.0.3 28 Jul 2024 none MIT — Details →
13.0.2 04 Jul 2024 none MIT — Details →
13.0.1 24 Jun 2024 none MIT — Details →
13.0.0 12 Jun 2024 none MIT — Details →
12.0.2 19 Apr 2024 none MIT — Details →
12.0.1 06 Mar 2024 none MIT — Details →
12.0.0 03 Feb 2024 none MIT — Details →
11.2.0 27 Jan 2024 none MIT — Details →
11.1.1 31 Dec 2023 none MIT — Details →
11.1.0 12 Dec 2023 none MIT — Details →
11.0.1 08 Dec 2023 none MIT — Details →
11.0.0 29 Nov 2023 none MIT — Details →
10.0.0 11 Nov 2023 none MIT — Details →
9.1.6 10 Nov 2023 none MIT — Details →
9.1.5 02 Nov 2023 none MIT — Details →
9.1.4 31 Oct 2023 none MIT — Details →
9.1.3 28 Oct 2023 none MIT — Details →
9.1.2 13 Oct 2023 none MIT — Details →
9.1.1 11 Oct 2023 none MIT — Details →
9.1.0 05 Oct 2023 none MIT — Details →
9.0.3 18 Sep 2023 none MIT — Details →
9.0.2 16 Sep 2023 none MIT — Details →
9.0.1 15 Sep 2023 none MIT — Details →
9.0.0 09 Sep 2023 none MIT — Details →
8.0.1 06 Sep 2023 none MIT — Details →
8.0.0 03 Sep 2023 none MIT — Details →
7.0.5 26 Aug 2023 none MIT — Details →
7.0.4 19 Aug 2023 none MIT — Details →
7.0.3 15 Aug 2023 none MIT — Details →
7.0.2 10 Aug 2023 none MIT — Details →
7.0.1 07 Aug 2023 none MIT — Details →
7.0.0 06 Aug 2023 none MIT — Details →
6.0.0 31 Jul 2023 none MIT — Details →
5.1.2 25 Jul 2023 none MIT — Details →
5.1.1 07 Jul 2023 none MIT — Details →
5.1.0 10 Jun 2023 none MIT — Details →
5.0.5 07 Jun 2023 none MIT — Details →
5.0.4 30 May 2023 none MIT — Details →
5.0.3 26 May 2023 none MIT — Details →
5.0.2 11 May 2023 none MIT — Details →
5.0.1 06 May 2023 none MIT — Details →
5.0.0 02 May 2023 none MIT — Details →
4.3.0 22 Mar 2023 none MIT — Details →
4.2.12 14 Jan 2023 none MIT — Details →
4.2.11 14 Jan 2023 none MIT — Details →
4.2.10 14 Jan 2023 none MIT — Details →
4.2.9 14 Jan 2023 none MIT — Details →
4.2.8 14 Jan 2023 none — — Details →
4.2.7 14 Jan 2023 none — — Details →
4.2.6 14 Jan 2023 none — — Details →
4.2.5 23 Dec 2022 none — — Details →
4.2.4 07 Dec 2022 none — — Details →
4.2.3 20 Nov 2022 none — — Details →
4.2.2 05 Nov 2022 none — — Details →
4.2.1 02 Nov 2022 none — — Details →
4.2.0 31 Oct 2022 none — — Details →
4.1.1 01 Oct 2022 none — — Details →
4.1.0 30 Aug 2022 none — — Details →
4.0.19 21 Aug 2022 none — — Details →
4.0.18 11 Jul 2022 none — — Details →
4.0.17 13 Jun 2022 none — — Details →
4.0.16 17 May 2022 none — — Details →
4.0.15 02 May 2022 none — — Details →
4.0.14 11 Apr 2022 none — — Details →
4.0.13 08 Apr 2022 none — — Details →
4.0.12 27 Jan 2022 none — — Details →
4.0.11 26 Jan 2022 none — — Details →

The newest 120 of 227 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2018 3
  • 2019 2
  • 2020 3
  • 2021 4
  • 2022 2
  • 2025 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for marked

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-16114: Regular Expression Denial of Service in marked 7.5 high 0.3.9 24 Jul 2018
CVE-2022-21681: Inefficient Regular Expression Complexity in marked 7.5 high 4.0.10 14 Jan 2022
CVE-2026-41680: Denial of Service Vulnerability in marked Package Due to Infinite Recursion 7.5 high 18.0.2 29 Apr 2026
CVE-2022-21680: Inefficient Regular Expression Complexity in marked 7.5 high 4.0.10 14 Jan 2022
CVE-2015-8854: Regular Expression Denial of Service in marked 7.5 high 0.3.4 24 Oct 2017

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 marked

Is marked safe to use?

Vulert records 18 vulnerabilities for marked in npm: 0 critical, 5 high, 12 medium and 1 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 marked's Vulert package health score?

Vulert scores marked 83/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 marked affected?

No. 18.1.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.

How many vulnerabilities does marked have?

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

How often are new marked vulnerabilities disclosed?

1 vulnerability was recorded for marked in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 marked 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 marked for upcoming vulnerabilities?

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