CVE-2026-49453 json
Joplin: Path traversal in resource sync — silent arbitrary file write outside the resource directory
published 2mo ago modified last mo. also EUVD-2026-84167 , GHSA-r24r-gp6h-cwgf
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository laurent22/joplin. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Joplin is an open source note-taking and to-do application that organises notes and lists into notebooks. Prior to 3.6.15 and 3.7.2, Joplin accepts synchronized resource metadata whose id or file_extension contains parent-directory or path-separator characters. BaseItem.unserialize() stores the unvalidated fields, resourceFilename() concatenates them into a destination path, and ResourceFetcher writes the attacker-controlled resource blob outside the resource directory during background synchronization. An attacker with write access to a configured sync target or shared notebook can create or overwrite files at an attacker-chosen existing path without user interaction. This issue is fixed in versions 3.6.15 and 3.7.2.
Patch / fix
- npm joplin 3.7.2
- joplin_project joplin 3.6.15, 3.7.2
- github.com/laurent22/joplin@18e0b08 commit
- github.com/laurent22/joplin@5051807 commit
- github.com/laurent22/joplin#15540 pull request
- github.com/laurent22/joplin#15672 pull request
Is CVE-2026-49453 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/laurent22/joplin/security/advisories/GHSA-r24r-gp6h-cwgf referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | joplin | <=3.7.1 |
3.7.2 |
Affected products
- laurent22 joplin
Classification
References
- github.com /laurent22/joplin/pull/15540
- github.com /laurent22/joplin/pull/15672
- github.com /laurent22/joplin/commit/18e0b08c282c89ae51612c4eff67af2a45ff5163
- github.com /laurent22/joplin/commit/50518073740c4501058e366300b42c2f1925cb05
-
github.com
/laurent22/joplin/security/advisories/GHSA-r24r-gp6h-cwgf
exploit, advisory
Sources
- CVE List CVE-2026-49453
- NVD CVE-2026-49453
- Maintainer advisory GHSA-r24r-gp6h-cwgf
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of laurent22/joplin published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.