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.
CVE-2026-55179
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
September 21, 2026
Last Modified
September 23, 2026
Advisory Details (3)
Auto-updated Sep 21, 2026Logic error in Joplin Server allows a signed-in user to read any note from its internal server ID · Advisory · laurent22/joplin · GitHub
https://github.com/laurent22/joplin/security/advisories/GHSA-r865-g55x-3mfcServer: Improve `items/` route validation logic
Fix merged in laurent22/joplin PR #15657 on 2026-06-12 — awaiting tagged release
https://github.com/laurent22/joplin/pull/15657commit 63dfa3b5ab47 (laurent22/joplin)
Fix landed in laurent22/joplin commit 63dfa3b5ab47 — awaiting tagged release
https://github.com/laurent22/joplin/commit/63dfa3b5ab47f29129348b4cd3a161a2dce6bc0eWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 19:42 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 18:39 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 15:23 UTCEG score recompute
- 2026-09-22 14:20 UTCEG score recompute
- 2026-09-22 13:27 UTCEG score recompute
- 2026-09-21 21:22 UTCEG score recompute
- 2026-09-21 21:02 UTCEG score recompute
- 2026-09-21 21:01 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-55179?
When was CVE-2026-55179 disclosed?
Is CVE-2026-55179 actively exploited?
What is the CVSS score of CVE-2026-55179?
How do I remediate CVE-2026-55179?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55179
Is Your Infrastructure Affected by CVE-2026-55179?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.