CVE-2022-35131: Arbitrary Code Execution in Joplin

joplin Updated 02 Oct 2025

Summary

26/07/2022
Yes i
Critical
9.0

CVE-2022-35131: Joplin is vulnerable to arbitrary code execution. Affects joplin versions < 2.9.1. Fixed in 2.9.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Joplin is an open-source note-taking and to-do application that allows users to organize their thoughts, tasks, and ideas. It is widely used for its cross-platform compatibility and synchronization capabilities. However, a critical vulnerability has been discovered in Joplin version 2.8.8, which exposes it to arbitrary code execution attacks. This vulnerability can be exploited by injecting a specially crafted payload into the Node titles, enabling attackers to execute arbitrary commands on the affected system.

Vulnerability Detail

The vulnerability (CVE-2022-35131) in Joplin arises from inadequate input validation in the handling of Node titles. By manipulating the payload injected into the titles, an attacker can execute arbitrary commands with the privileges of the user running the Joplin application. This could lead to various malicious activities, such as unauthorized access, data theft, or even complete compromise of the affected system. The severity of this vulnerability is rated as critical (CVSS score: 9.0).

How To Fix

Minimum fixed version

2.9.1

This is the first release that contains the fix.

npm install joplin@2.9.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, users can refrain from using or interacting with Node titles until the Joplin application has been updated to a secure version. This reduces the risk of exploitation but does not eliminate it entirely. It is strongly advised to apply the official fix as soon as possible.

Conclusion

Joplin version 2.8.8 is vulnerable to arbitrary code execution due to inadequate input validation in Node titles. This critical vulnerability can be exploited by attackers to execute arbitrary commands on the affected system. To mitigate the risk, users should upgrade Joplin to version 2.9.1 or later. It is recommended to follow the official upgrade instructions provided by the Joplin project. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for joplin →

Share this vulnerability

FAQ

Joplin is an open-source note-taking and to-do application that helps users organize their thoughts, tasks, and ideas. It offers cross-platform compatibility and synchronization capabilities.

The vulnerability allows attackers to execute arbitrary commands on the affected system. This can lead to unauthorized access, data theft, or complete compromise of the system.

To fix this vulnerability, update Joplin to version 2.9.1 or later. Follow the official upgrade instructions provided by the Joplin project.

As a temporary workaround, avoid using or interacting with Node titles until the Joplin application is updated to a secure version.

The severity of this vulnerability is rated as critical, with a CVSS score of 9.0.

Related vulnerabilities

Recent vulnerabilities recorded for joplin.

How To Fix

Minimum fixed version

2.9.1

This is the first release that contains the fix.

npm install joplin@2.9.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback