How severe is GHSA-x949-7cm6-fm6p?

GHSA-x949-7cm6-fm6p has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-x949-7cm6-fm6p?

GHSA-x949-7cm6-fm6p affects the following packages: md-to-pdf (npm). Ecosystems affected: npm.

How do I fix GHSA-x949-7cm6-fm6p?

Update md-to-pdf to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x949-7cm6-fm6p is resolved across your whole dependency graph.

How do I detect GHSA-x949-7cm6-fm6p in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for md-to-pdf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-x949-7cm6-fm6p if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-x949-7cm6-fm6p?

O3 pinpoints whether GHSA-x949-7cm6-fm6p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-x949-7cm6-fm6p actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-x949-7cm6-fm6p, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-x949-7cm6-fm6p?

GHSA-x949-7cm6-fm6p has an EPSS (Exploit Prediction Scoring System) score of 5.3%, placing it in the 92th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-x949-7cm6-fm6p published, and has it been updated?

GHSA-x949-7cm6-fm6p was published on December 16, 2021 and was last updated on March 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-x949-7cm6-fm6p

CRITICAL

Code Injection in md-to-pdf.

Also known asCVE-2021-23639

Published

Dec 16, 2021

Updated

Mar 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

5.3%probability of exploitation in next 30 days

Lower Risk92th percentile-14.58%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

md-to-pdfnpm

140Kdownloads / week

Description

The package md-to-pdf before 5.0.0 are vulnerable to Remote Code Execution (RCE) due to utilizing the library gray-matter to parse front matter content, without disabling the JS engine.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`md-to-pdf`	all versions	5.0.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The package md-to-pdf before 5.0.0 are vulnerable to Remote Code Executi…

snyk.ioNVDDec 2021

The package md-to-pdf before 5.0.0 are vulnerable to Remote Code Executi…

github.comNVDDec 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for md-to-pdf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update md-to-pdf to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x949-7cm6-fm6p is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-x949-7cm6-fm6p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-x949-7cm6-fm6p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The package md-to-pdf before 5.0.0 are vulnerable to Remote Code Execution (RCE) due to utilizing the library gray-matter to parse front matter content, without disabling the JS engine.

O3 Security · Impact-Aware SCA

Is GHSA-x949-7cm6-fm6p in your dependencies?

O3 detects GHSA-x949-7cm6-fm6p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works