VulertSecurity VulertSecurity

Vulnerability Database · Ubuntu · Package report

node-marked: vulnerability history, versions and safety

node-marked is a package in the Ubuntu ecosystem. Vulert records 9 vulnerabilities for it across 1 release, from Jan 2015 to May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded U9
i
9 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all node-marked vulnerabilities

Vulert verdict on node-marked i

Updated on 23 Oct 2026

Careful: 9 of the 9 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 9 vulnerabilities on record across 10 years, none in the last year.

What to do: Plan around the 9 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 9 over 10 years · 0 in the last year i
  • Latest disclosure 23 May 2025 i
  • Highest CVSS 7.5 i
  • With no published fix 9 i

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 holds for node-marked, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
0.3.2+dfsg-1 U9 No Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2015 1
  • 2017 2
  • 2018 3
  • 2022 2
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for node-marked

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in Node.js Package 'marked' - CVE-2015-8854 7.5 high No fix published 23 Jan 2017
Regular Expression Denial of Service in Node-marked Package - CVE-2017-16114 7.5 high No fix published 07 Jun 2018
Denial of Service Vulnerability in Node-marked Package: CVE-2022-21681 7.5 high No fix published 14 Jan 2022
Critical Vulnerability in Node-marked Package: Regular Expression Denial of Service (ReDoS) 7.5 high No fix published 14 Jan 2022
Denial of Service Vulnerability in Node-marked Package: CVE-2018-25110 6.9 medium No fix published 23 May 2025

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 node-marked

Is node-marked safe to use?

Vulert records 9 vulnerabilities for node-marked in Ubuntu: 0 critical, 0 high, 0 medium and 0 low, plus 9 not yet rated. 9 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does node-marked have?

9 vulnerabilities are recorded for node-marked in the Ubuntu ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 9 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new node-marked vulnerabilities disclosed?

0 vulnerabilities were recorded for node-marked in the last 12 months, and the oldest entry in this database dates to 27 Jan 2015. 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 node-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 node-marked for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the node-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.