# CVE-2026-46650: Joplin: Stored XSS in public share viewer via javascript: URL bypass in isAcceptedUrl

> A low-privileged user can inject JavaScript into public notes via a bypassed URL check, allowing script execution in the victim's browser context.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-x9vj-jrqf-9wcm

## What is CVE-2026-46650?

CVE-2026-46650 is a medium-severity cross-site scripting vulnerability in laurent22 joplin, published on 21 Sep 2026. Any signed-in user can exploit it over the network, 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.2, isAcceptedUrl() in packages/renderer/htmlUtils.ts uses an unanchored regular expression for internal resource URLs, allowing a javascript: URL containing a matching 32-character path fragment to pass validation and be emitted into an HTML note's link. A low-privileged Joplin Server user can publish the crafted HTML note as a public share. In the current build, ordinary left-click is blocked; demonstrated execution requires middle-click or Open in new tab in an older or non-hardened browser because current Chrome and Firefox block javascript: new-tab navigation. When execution succeeds, the script runs in the Joplin Server origin, can read page-visible content, and can make authenticated same-origin requests when the victim is signed in. This issue is fixed in version 3.7.2.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-46650 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46650 is a medium-severity cross-site scripting vulnerability in laurent22 joplin, published on 21 Sep 2026. Any signed-in user can exploit it over the network, 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-46650 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-46650/ (Markdown: https://insights.sbomify.com/CVE-2026-46650/index.md)
```

## Sources

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

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