CVE-2026-22810
Path Traversal in Joplin Note-Taking App
Publication date: 2026-05-18
Last updated on: 2026-05-19
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| joplin | joplin | to 3.5.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-24 | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in Joplin's OneNote importer allows an attacker to overwrite arbitrary files on disk by exploiting a path traversal flaw. This could lead to unauthorized modification or corruption of sensitive files on a user's system.
Such unauthorized file overwriting could potentially result in breaches of data integrity and confidentiality, which are critical aspects of compliance with standards like GDPR and HIPAA.
If sensitive personal or health information stored or processed by Joplin is affected by this vulnerability, organizations using vulnerable versions might face compliance risks due to potential data tampering or loss.
However, the provided information does not explicitly discuss direct impacts on compliance frameworks or regulatory requirements.
Can you explain this vulnerability to me?
This vulnerability exists in Joplin, an open source note-taking and to-do application, in versions prior to 3.5.7. It is a path traversal vulnerability in the importer, specifically in the OneNote converter. The issue arises because the converter does not sanitize the names of embedded files before writing them to disk. An attacker can create a malicious .one file containing file names with path traversal sequences like "../../". When these files are extracted, the paths are interpreted as part of the target location, allowing the attacker to overwrite arbitrary files on the disk.
How can this vulnerability impact me? :
This vulnerability can have severe impacts because it allows an attacker with limited privileges to overwrite arbitrary files on the disk. This can lead to complete compromise of the system's integrity, including the possibility of executing malicious code, corrupting important files, or disrupting system operations. The CVSS score of 8.2 indicates a high severity with impacts on confidentiality, integrity, and availability.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is patched in Joplin version 3.5.7. To mitigate this vulnerability, you should immediately upgrade your Joplin installation to version 3.5.7 or later.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves a path traversal issue in the Joplin OneNote importer that allows overwriting arbitrary files on disk via malicious .one files containing filenames with "../" sequences.
To detect exploitation attempts or presence of this vulnerability on your system, you can look for unexpected modifications to sensitive files such as .bashrc or Joplin's log.txt, especially if these files have been recently changed without your knowledge.
Since the vulnerability is triggered by importing crafted .one files, monitoring file system changes during or after imports can help detect suspicious activity.
Suggested commands to help detect potential exploitation or presence of malicious files include:
- Check for recently modified sensitive files (e.g., ~/.bashrc, log files): find /home/username -name ".bashrc" -mtime -7 -ls
- Search for files containing path traversal patterns in filenames within Joplin data directories: find /path/to/joplin/data -type f -name "*..*"
- Monitor file system audit logs for unexpected writes during import operations if auditing is enabled.
Note that no specific detection commands or signatures are provided in the available resources, so detection relies on monitoring file changes and suspicious filenames related to the import process.