# CVE-2022-41710: Markdownify has Files or Directories Accessible to External Parties

> An attacker can read arbitrary local files on a client by tricking them into viewing a malicious markdown file in Markdownify.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Nov 2022
- **Updated:** 5 May 2025
- **Also known as:** GHSA-qqhf-xfhw-7884

## What is CVE-2022-41710?

CVE-2022-41710 is a medium-severity path traversal vulnerability in Markdownify, published on 3 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Markdownify version 1.4.1 allows an external attacker to remotely obtain arbitrary local files on any client that attempts to view a malicious markdown file through Markdownify. This is possible because the application does not have a CSP policy (or at least not strict enough) and/or does not properly validate the contents of markdown files before rendering them.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2022-41710?

2 open source packages ship an affected version, including electron-markdownify. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `electron-markdownify` | npm | All versions to 1.4.1 | None |
| `electron-markdownify` | npm | All versions to 1.4.1 | None |

Products: Markdownify Project Markdownify.

## How do I fix CVE-2022-41710?

No fix has been published for CVE-2022-41710 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41710 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41710 exists.

## Other vulnerabilities in Markdownify

- [CVE-2022-41709](https://insights.sbomify.com/CVE-2022-41709/): Markdownify subject to Remote Code Execution via malicious markdown file (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41710 and fix it if it is affected.

What it is: CVE-2022-41710 is a medium-severity path traversal vulnerability in Markdownify, published on 3 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41710 exists.

Affected packages and fixed versions:
- electron-markdownify (npm): affected all versions up to 1.4.1; no fix listed
- electron-markdownify (npm): affected all versions up to 1.4.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41710/ (Markdown: https://insights.sbomify.com/CVE-2022-41710/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41710
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41710
- OSV: https://osv.dev/vulnerability/CVE-2022-41710

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41710/
Summaries are generated and may contain mistakes; the official description above is the record.