Joplin is an open source note-taking and to-do application that organises notes and lists into notebooks. Prior to 3.7.2, Joplin Desktop for Windows omits publisherName from packages/app-desktop/package.json, so the generated app-update.yml causes NsisUpdater.verifySignature() to skip comparison of a downloaded update's Authenticode signer with Joplin's signer. An attacker who controls the update delivery path can replace the update metadata and installer, and the client accepts an installer signed by another publisher or left unsigned after the user approves installation. Successful exploitation runs attacker-controlled code with the user's privileges and can compromise notes, credentials, and local data. This issue is fixed in version 3.7.2.
CVE-2026-49450
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 48(Track*)EG Risk 48/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 computedSeverity71% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
September 21, 2026
Last Modified
September 23, 2026
Advisory Details (3)
Auto-updated Sep 21, 2026Joplin desktop Windows auto-updater accepts signed installer from any publisher because app-update.yml has no publisherName · Advisory · laurent22/joplin · GitHub
https://github.com/laurent22/joplin/security/advisories/GHSA-9wp7-hr9m-3273Desktop: Set Windows publisher name for installer verification
Fix merged in laurent22/joplin PR #15539 on 2026-05-27 — awaiting tagged release
https://github.com/laurent22/joplin/pull/15539commit 853659edf575 (laurent22/joplin)
Fix landed in laurent22/joplin commit 853659edf575 — awaiting tagged release
https://github.com/laurent22/joplin/commit/853659edf575c4f526c2b196e0629462aee9df28Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× 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 16:21 UTCEG score recompute
- 2026-09-23 18:39 UTCEG score recompute
- 2026-09-23 17:53 UTCEPSS rescore
- 2026-09-23 01:12 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 20:58 UTCEG score recompute
- 2026-09-21 20:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-49450?
When was CVE-2026-49450 disclosed?
Is CVE-2026-49450 actively exploited?
What is the CVSS score of CVE-2026-49450?
How do I remediate CVE-2026-49450?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-49450
Is Your Infrastructure Affected by CVE-2026-49450?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.