CVE-2022-36036: mdx-mermaid provides plug and play access to Mermaid in MDX

Q: How do I fix CVE-2022-36036?

mdx-mermaid: upgrade to 1.3.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-36036 being exploited?

CVE-2022-36036 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-36036 affect?

CVE-2022-36036 affects mdx-mermaid. Severity is low (CVSS 3.6). mdx-mermaid provides plug and play access to Mermaid in MDX. There is a potential for an arbitrary javascript injection in versions less than 1.3.0 and 2.0.0-rc1. Modify any mermaid code blocks with arbitrary code and it will execute when t

Q: How urgent is CVE-2022-36036?

Priority 26/100. Public exploit reference

Routine

LOW 3.6UPGRADE

CVE-2022-36036 is a low-severity flaw (CVSS 3.6) affecting mdx-mermaid. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

mdx-mermaid provides plug and play access to Mermaid in MDX. There is a potential for an arbitrary javascript injection in versions less than 1.3.0 and 2.0.0-rc1. Modify any mermaid code blocks with arbitrary code and it will execute when the component is loaded by MDXjs. This vulnerability was patched in version(s) 1.3.0 and 2.0.0-rc2. There are currently no known workarounds.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	3.6 (Low)
Attack vector	Local
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-94
Published	2022-08-29
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: mdx-mermaid project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-08-29 18:15 UTCPublished CVE record published
2026-06-17 04:52 UTCUpdated Record last modified

mdx-mermaid project mdx-mermaid UPGRADE

Affected: >= 0.0.1 and < 1.3.0 · 2.0.0 rc1

Fixed in: 1.3.0

Safe to downgrade to: a release before 0.0.1

1. Check installed version

npm ls mdx-mermaid

2. UPGRADE to 1.3.0

npm install mdx-mermaid@">=1.3.0"

3. If no update is available yet, DOWNGRADE to a release before 0.0.1

npm view mdx-mermaid versions npm install mdx-mermaid@"<0.0.1"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-36036?

mdx-mermaid: upgrade to 1.3.0. Exact commands for each OS are on this page.

Is CVE-2022-36036 being exploited?

CVE-2022-36036 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-36036 affect?

CVE-2022-36036 affects mdx-mermaid. Severity is low (CVSS 3.6). mdx-mermaid provides plug and play access to Mermaid in MDX. There is a potential for an arbitrary javascript injection in versions less than 1.3.0 and 2.0.0-rc1. Modify any mermaid code blocks with arbitrary code and it will execute when t

How urgent is CVE-2022-36036?

Priority 26/100. Public exploit reference

References

← Back to latest CVEs