NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2024-21535 — markdown-to-jsx

MEDIUMFix: quantizor/markdown-to-jsx@8eb74da

CVE-2024-21535 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in markdown-to-jsx. A fix is available for markdown-to-jsx — see the affected versions and patch details below.

Cross site scripting in markdown-to-jsx

Also known asGHSA-4wx3-54gh-9fr9
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-21535.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk
0.00%0.34%0.68%1.02%0.2%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

589other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
markdown-to-jsxnpm
5.9Mdownloads / week

Description

Versions of the package markdown-to-jsx before 7.4.0 are vulnerable to Cross-site Scripting (XSS) via the src property due to improper input sanitization. An attacker can execute arbitrary code by injecting a malicious iframe element in the markdown.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmmarkdown-to-jsxall versions7.4.0npm install markdown-to-jsx@7.4.0

Affected Products

1 product · 1 configurations
Application
markdown-to-jsxquantizor
< 7.4.0
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for markdown-to-jsx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update markdown-to-jsx to 7.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-21535 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2024-21535 (CC BY 4.0)

Frequently Asked Questions

Versions of the package markdown-to-jsx before 7.4.0 are vulnerable to Cross-site Scripting (XSS) via the src property due to improper input sanitization. An attacker can execute arbitrary code by injecting a malicious iframe element in the markdown.
O3 Security · Impact-Aware SCA

Is CVE-2024-21535 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2024-21535: markdown-to-jsx RCE — Fixed in 7.4.0