# CVE-2026-105786: Joplin: Unauthenticated account takeover via an attacker-chosen application-authorisation identifier

> An attacker can hijack a victim's Joplin account by tricking them into approving a malicious application authorization identifier, gaining full data access.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-435m-gr6q-2fg6

## What is CVE-2026-105786?

CVE-2026-105786 is a high-severity authentication bypass vulnerability in laurent22 joplin, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Joplin is an open source note-taking and to-do application that organises notes and lists into notebooks. Prior to 3.7.13, packages/server/src/models/ApplicationModel.ts accepts a caller-chosen application authorization identifier, applications/:id/confirm binds that identifier to a logged-in user through a generic consent page, and the public packages/server/src/routes/api/application_auth.ts endpoint passes it to ApplicationModel.createAppPassword without authenticating or binding the redeemer. An attacker can cause a victim to approve the attacker's identifier, redeem a durable application ID and password, and exchange the credential for a victim session with full read and write access to synchronized data. This vulnerability is fixed in 3.7.13.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-863 (Incorrect Authorization), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-105786?


## How do I fix CVE-2026-105786?

No fix has been published for CVE-2026-105786 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105786 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105786 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105786 and fix it if it is affected.

What it is: CVE-2026-105786 is a high-severity authentication bypass vulnerability in laurent22 joplin, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105786 exists.

Affected product: laurent22 joplin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105786/ (Markdown: https://insights.sbomify.com/CVE-2026-105786/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105786
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105786
- OSV: https://osv.dev/vulnerability/CVE-2026-105786

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105786/
Summaries are generated and may contain mistakes; the official description above is the record.