Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

CVE-2020-12827

HIGHFix: mjmlio/mjml@30e29ed

CVE-2020-12827 is a high-severity (CVSS 7.2) Path Traversal vulnerability in mjml. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2020-12827 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

MJML vulnerable to path traversal

Also known asGHSA-4hch-r9xf-6vfr
Published
Jun 17, 2020
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
2 known

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

mjmlnpm
1.8Mdownloads / week

Description

MJML prior to 4.6.3 contains a path traversal vulnerability when processing the mj-include directive within an MJML document.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmmjmlall versions4.6.3
Exploits & PoCs
2

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

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mjml. 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.

  2. Fix

    Update mjml to 4.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-12827 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2020-12827 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 CVE-2020-12827. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

MJML prior to 4.6.3 contains a path traversal vulnerability when processing the mj-include directive within an MJML document.
O3 Security · Impact-Aware SCA

Is CVE-2020-12827 in your dependencies?

O3 detects CVE-2020-12827 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.