Quick answers
- Is CVE-2026-105783 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105783 being exploited in the wild.
- How severe is CVE-2026-105783?
- High severity, with a CVSS score of 8, published 6 October 2026.
- Which products and versions are affected?
- Joplin Desktop before 3.7.13.
- Is there a fix for CVE-2026-105783?
- Yes: fixed in 3.7.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105783 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105783?
- Check whether you run Joplin Desktop 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.
How to fix
- Fixed in: 3.7.13
Technical details
The Web Clipper server in ClipperServer.ts responds to POST /auth and GET /auth/check endpoints with Access-Control-Allow-Origin: * and does not validate the origin of pairing requests, allowing arbitrary websites to initiate authentication. The desktop confirmation dialog shown to the user does not display the requesting origin, making it impossible for the user to identify malicious requests before granting a permanent API token. An attacker can craft a webpage that triggers the pairing flow and, upon user approval, receives an API token providing full read/write access to notes, folders, tags, resources, and cryptographic keys.
Affected products
- Joplin Desktop before 3.7.13
Timeline
- 2026-10-06: disclosed
- 2026-08-22: patched