CVE-2026-46650

MEDIUMPre-NVD 4.44.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-84180 (ENISA EUVD)Source: ENISA EUVD

4.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.4Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
36
EG Risk 36/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 21, 2026

Last Modified

September 29, 2026

Advisory Details (3)

Auto-updated Sep 21, 2026
Fix named in the CVE record. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)

Stored XSS in public share viewer via javascript: URL bypass in isAcceptedUrl · Advisory · laurent22/joplin · GitHub

https://github.com/laurent22/joplin/security/advisories/GHSA-x9vj-jrqf-9wcm
GitHub pull request

Server, Desktop, Mobile: Fix XSS vulnerability in HTML notes

Fix merged in laurent22/joplin PR #15435 on 2026-05-15 — awaiting tagged release

https://github.com/laurent22/joplin/pull/15435
GitHub commit

commit 9fdc2d4adbd7 (laurent22/joplin)

Fix landed in laurent22/joplin commit 9fdc2d4adbd7 — awaiting tagged release

https://github.com/laurent22/joplin/commit/9fdc2d4adbd7b7326a2d0dcc32e12b705bfc285e

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-10-30 14:55 UTCOSV refresh
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-25 14:25 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-22 23:22 UTCEG score recompute
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-10-18 03:36 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
Show 45 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-10-12 16:02 UTCEG score recompute
  4. 2026-10-11 19:45 UTCEG score recompute
  5. 2026-10-11 16:59 UTCEG score recompute
  6. 2026-10-11 14:25 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-10-11 13:10 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-10-10 12:36 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-10-09 12:50 UTCEG score recompute
  13. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-08 12:33 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-07 12:48 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-06 12:36 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-10-05 12:52 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-04 13:07 UTCEG score recompute
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-03 13:20 UTCEG score recompute
  25. 2026-10-02 13:36 UTCEG score recompute
  26. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  27. 2026-10-01 13:48 UTCEG score recompute
  28. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  29. 2026-09-30 14:04 UTCEG score recompute
  30. 2026-09-29 14:19 UTCEG score recompute
  31. 2026-09-29 14:04 UTCEG score recompute
  32. 2026-09-28 18:15 UTCEG score recompute
  33. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  34. 2026-09-27 17:50 UTCEG score recompute
  35. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  36. 2026-09-26 18:05 UTCEG score recompute
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  38. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  39. 2026-09-24 18:23 UTCEG score recompute
  40. 2026-09-23 18:39 UTCEG score recompute
  41. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  42. 2026-09-22 22:11 UTCEG score recompute
  43. 2026-09-21 22:27 UTCEG score recompute
  44. 2026-09-21 21:27 UTCEG score recomputeFirst assessed: 4.4 MEDIUM
  45. 2026-09-21 21:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46650?
CVE-2026-46650 is a medium-severity vulnerability; its CVE record was published on September 21, 2026. 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…
When was the CVE record for CVE-2026-46650 published?
The CVE record for CVE-2026-46650 was published on September 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2026-46650 actively exploited?
CVE-2026-46650 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46650?
CVE-2026-46650 has a CVSS base score of 4.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46650?
The CVE record for CVE-2026-46650 names the fix: "This issue is fixed in version 3.7.2."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46650

Explore →

Is Your Infrastructure Affected by CVE-2026-46650?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs