Skip to content

← Actionable
High, CVSS 7.8amended

Markdownify subject to Remote Code Execution via malicious markdown file

CVE-2022-41709GHSA-c942-mfmp-p4fh

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm electron-markdownify

    Affected
    <= 1.4.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.8 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
  • CVE-2022-41709: 0.48% estimated exploitation activity in the next 30 days; percentile 41.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Markdownify version 1.4.1 allows an external attacker to execute arbitrary code remotely on any client attempting to view a malicious markdown file through Markdownify. This is possible because the application has the "nodeIntegration" option enabled. There are currently no patched versions and no known workarounds.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-c942-mfmp-p4fh

  2. Revision 1 · created ·

    Published from osv record GHSA-c942-mfmp-p4fh

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-41709

Advisory: Markdownify subject to Remote Code Execution via malicious markdown file
IDs: CVE-2022-41709, GHSA-c942-mfmp-p4fh
Record: https://patchnext.com/advisories/cve-2022-41709 (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron-markdownify: affected <= 1.4.1

## Suggested inspection (read-only)
- `npm ls electron-markdownify --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on electron-markdownify.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-c942-mfmp-p4fh (OSV record GHSA-c942-mfmp-p4fh lists affected ranges: npm electron-markdownify >=0 <=1.4.1)
- Verified: https://github.com/advisories/GHSA-c942-mfmp-p4fh (GitHub-reviewed advisory GHSA-c942-mfmp-p4fh lists affected ranges: npm electron-markdownify >=0 <=1.4.1)

Commands are suggestions: review each one before running it.

Loading voting…