Quick answers
- Is CVE-2026-49453 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49453 being exploited in the wild.
- How severe is CVE-2026-49453?
- High severity, with a CVSS score of 7, published 21 September 2026.
- Which products and versions are affected?
- Joplin before 3.6.15 and before 3.7.2.
- Is there a fix for CVE-2026-49453?
- A patch was published on 2026-06-20: Fix merged to reject malformed item IDs and improve resource filename determination Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49453 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-49453?
- Check whether you run Joplin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a path traversal flaw in resource metadata handling. BaseItem.unserialize() fails to validate the id or file_extension fields before passing them to resourceFilename(), which concatenates them into a destination path. ResourceFetcher then writes attacker-controlled resource blobs outside the intended resource directory during sync. An attacker needs write access to the sync target or notebook.
Affected products
- Joplin Joplin before 3.6.15 and before 3.7.2
Timeline
- 2026-09-21: disclosed
- 2026-06-20: patched: Fix merged to reject malformed item IDs and improve resource filename determination