# CVE-2026-55179: Joplin: Logic error in Joplin Server allows a signed-in user to read any note from its internal server ID

> An authenticated user can read any note content by guessing internal IDs due to missing ownership checks in Joplin Server.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-r865-g55x-3mfc

## What is CVE-2026-55179?

CVE-2026-55179 is a medium-severity missing authorization vulnerability in laurent22 joplin, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Joplin is an open source note-taking and to-do application that organises notes and lists into notebooks. Prior to 3.7.2, Joplin Server's GET /items/:id/content route in packages/server/src/routes/index/items.ts loads item content from an attacker-supplied internal server ID without checking whether the signed-in user owns or can access that item. Any authenticated user who obtains or guesses another user's item ID can read the corresponding note or item content when end-to-end encryption does not protect it. This issue is fixed in version 3.7.2.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-55179 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55179 is a medium-severity missing authorization vulnerability in laurent22 joplin, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55179 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-55179/ (Markdown: https://insights.sbomify.com/CVE-2026-55179/index.md)
```

## Sources

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

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