VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

markdown-to-jsx: vulnerability history, versions and safety

markdown-to-jsx is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 28 releases, from Sep 2020 to Oct 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 markdown-to-jsx vulnerabilities

Vulert verdict on markdown-to-jsx 9.10.3 i

Updated on 23 Oct 2026

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

Package health score 92/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 9.10.3 — unaffected i
  • Vulnerabilities on record 2 over 4 years · 0 in the last year i
  • Latest disclosure 15 Oct 2024 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 207 packages i
  • Stars 2,395 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 markdown-to-jsx, 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
9.10.3 15 Sep 2026 none MIT — Details →
9.10.2 03 Aug 2026 none MIT — Details →
9.10.1 31 Jul 2026 none MIT — Details →
9.10.0 31 Jul 2026 none MIT — Details →
9.9.0 20 Jul 2026 none MIT — Details →
9.8.2 10 Jun 2026 none MIT — Details →
9.8.1 20 May 2026 none MIT — Details →
9.8.0 11 May 2026 none MIT — Details →
9.7.16 17 Apr 2026 none MIT — Details →
9.7.15 08 Apr 2026 none MIT — Details →
9.7.14 07 Apr 2026 none MIT — Details →
9.7.13 21 Mar 2026 none MIT — Details →
9.7.12 20 Mar 2026 none MIT — Details →
9.7.11 19 Mar 2026 none MIT — Details →
9.7.10 19 Mar 2026 none MIT — Details →
9.7.9 10 Mar 2026 none MIT — Details →
9.7.8 06 Mar 2026 none MIT — Details →
9.7.7 06 Mar 2026 none MIT — Details →
9.7.7-prerelease.0 04 Mar 2026 none MIT — Details →
9.7.6 20 Feb 2026 none MIT — Details →
9.7.5 19 Feb 2026 none MIT — Details →
9.7.5-prerelease.0 19 Feb 2026 none MIT — Details →
9.7.4 13 Feb 2026 none MIT — Details →
9.7.3 06 Feb 2026 none MIT — Details →
9.7.2 04 Feb 2026 none MIT — Details →
9.7.2-prerelease.0 04 Feb 2026 none MIT — Details →
9.7.1 04 Feb 2026 none MIT — Details →
9.7.1-prerelease.4 04 Feb 2026 none MIT — Details →
9.7.1-prerelease.3 04 Feb 2026 none MIT — Details →
9.7.1-prerelease.2 04 Feb 2026 none MIT — Details →
9.7.1-prerelease.1 04 Feb 2026 none MIT — Details →
9.7.1-prerelease.0 04 Feb 2026 none MIT — Details →
9.7.0 04 Feb 2026 none MIT — Details →
9.6.1 22 Jan 2026 none MIT — Details →
9.6.0 20 Jan 2026 none MIT — Details →
9.5.7 13 Jan 2026 none MIT — Details →
9.5.6 12 Jan 2026 none MIT — Details →
9.5.5 11 Jan 2026 none MIT — Details →
9.5.4 11 Jan 2026 none MIT — Details →
9.5.3 10 Jan 2026 none MIT — Details →
9.5.2 10 Jan 2026 none MIT — Details →
9.5.1 08 Jan 2026 none MIT — Details →
9.5.0 21 Dec 2025 none MIT — Details →
9.4.3-prerelease 21 Dec 2025 none MIT — Details →
9.4.2 17 Dec 2025 none MIT — Details →
9.4.1 17 Dec 2025 none MIT — Details →
9.4.0 16 Dec 2025 none MIT — Details →
9.3.5 12 Dec 2025 none MIT — Details →
9.3.4 11 Dec 2025 none MIT — Details →
9.3.3 09 Dec 2025 none MIT — Details →
9.3.2 06 Dec 2025 none MIT — Details →
9.3.2-prerelease 06 Dec 2025 none MIT — Details →
9.3.1 06 Dec 2025 none MIT — Details →
9.3.0 30 Nov 2025 none MIT — Details →
9.2.0 28 Nov 2025 none MIT — Details →
9.1.2 26 Nov 2025 none MIT — Details →
9.1.1 22 Nov 2025 none MIT — Details →
9.1.0 22 Nov 2025 none MIT — Details →
9.0.0 22 Nov 2025 none MIT — Details →
9.0.0-rc.1 21 Nov 2025 none MIT — Details →
8.0.0 26 Oct 2025 none MIT — Details →
7.7.17 24 Oct 2025 none MIT — Details →
7.7.16 19 Oct 2025 none MIT — Details →
7.7.15 07 Oct 2025 none MIT — Details →
7.7.14 06 Oct 2025 none MIT — Details →
7.7.13 06 Aug 2025 none MIT — Details →
7.7.12 18 Jul 2025 none MIT — Details →
7.7.11 18 Jul 2025 none MIT — Details →
7.7.10 28 Jun 2025 none MIT — Details →
7.7.9 28 Jun 2025 none MIT — Details →
7.7.8 19 Jun 2025 none MIT — Details →
7.7.7 15 Jun 2025 none MIT — Details →
7.7.6 23 Apr 2025 none MIT — Details →
7.7.5 23 Apr 2025 none MIT — Details →
7.7.4 17 Feb 2025 none MIT — Details →
7.7.3 07 Jan 2025 none MIT — Details →
7.7.2 18 Dec 2024 none MIT — Details →
7.7.1 04 Dec 2024 none MIT — Details →
7.7.0 20 Nov 2024 none MIT — Details →
7.6.2 14 Nov 2024 none MIT — Details →
7.6.1 13 Nov 2024 none MIT — Details →
7.6.0 12 Nov 2024 none MIT — Details →
7.5.1 12 Nov 2024 none MIT — Details →
7.5.0 18 Aug 2024 none MIT — Details →
7.4.7 13 Apr 2024 none MIT — Details →
7.4.6 05 Apr 2024 none MIT — Details →
7.4.5 22 Mar 2024 none MIT — Details →
7.4.4 21 Mar 2024 none MIT — Details →
7.4.3 13 Mar 2024 none MIT — Details →
7.4.2 12 Mar 2024 none MIT — Details →
7.4.1 29 Jan 2024 none MIT — Details →
7.4.0 01 Jan 2024 none MIT — Details →
7.3.2 05 Aug 2023 M1 MIT Yes Details →
7.3.1 03 Aug 2023 M1 MIT Yes Details →
7.3.0 03 Aug 2023 M1 MIT Yes Details →
7.2.1 02 Jun 2023 M1 MIT Yes Details →
7.2.0 18 Mar 2023 M1 MIT Yes Details →
7.1.9 01 Feb 2023 M1 MIT Yes Details →
7.1.8 05 Dec 2022 M1 MIT Yes Details →
7.1.7 07 Mar 2022 M1 MIT Yes Details →
7.1.6 16 Jan 2022 M1 — Yes Details →
7.1.5 28 Nov 2021 M1 — Yes Details →
7.1.4 28 Nov 2021 M1 — Yes Details →
7.1.3 21 May 2021 M1 — Yes Details →
7.1.2 10 Mar 2021 M1 — Yes Details →
7.1.1 09 Jan 2021 M1 — Yes Details →
7.1.0 20 Nov 2020 M1 — Yes Details →
7.0.1 05 Oct 2020 M1 — Yes Details →
7.0.0 07 Sep 2020 M1 — Yes Details →
7.0.0-test.0 07 Sep 2020 M1 — Yes Details →
6.11.4 22 May 2020 M1 — Yes Details →
6.11.3 22 May 2020 H1 M1 — Yes Details →
6.11.2 19 May 2020 H1 M1 — Yes Details →
6.11.1 07 Apr 2020 H1 M1 — Yes Details →
6.11.0 05 Feb 2020 H1 M1 — Yes Details →
6.10.3 06 Aug 2019 H1 M1 — Yes Details →
6.10.2 30 May 2019 H1 M1 — Yes Details →
6.10.1 29 May 2019 H1 M1 — Yes Details →
6.10.0 29 May 2019 H1 M1 — Yes Details →
6.9.4 18 Apr 2019 H1 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for markdown-to-jsx

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-21535: Cross-site Scripting Vulnerability in markdown-to-jsx 6.1 medium 7.4.0 15 Oct 2024
Cross-Site Scripting in markdown-to-jsx N/A high 6.11.4 03 Sep 2020

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 markdown-to-jsx

Is markdown-to-jsx safe to use?

Vulert records 2 vulnerabilities for markdown-to-jsx in npm: 0 critical, 1 high, 1 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 markdown-to-jsx's Vulert package health score?

Vulert scores markdown-to-jsx 92/100, which reads as healthy. 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 markdown-to-jsx affected?

No. 9.10.3, 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 markdown-to-jsx should I use?

9.10.3 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 markdown-to-jsx have?

2 vulnerabilities are recorded for markdown-to-jsx in the npm ecosystem: 0 critical, 1 high, 1 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 markdown-to-jsx vulnerabilities disclosed?

0 vulnerabilities were recorded for markdown-to-jsx in the last 12 months, and the oldest entry in this database dates to 03 Sep 2020. 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 markdown-to-jsx 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 markdown-to-jsx for upcoming vulnerabilities?

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