Notesnook Desktop
Approved changes feed: RSS · Atom
cpe:2.3:a:streetwriters:notesnook_desktop:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Streetwriters (a6372962-5763-5fe0-a8e1-a63368eb76ea) |
|---|---|
| Product | Notesnook Desktop (4207e0c7-8cab-5269-91cd-c1393d06beee) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-42090 |
vulnerable | 2026-06-08 08:03:15.931726 |
Notesnook: RCE via stored XSS in note export rendering
CRITICAL (9.6)
Notesnook is a note-taking app focused on user privacy & ease of use. Prior to Notesnook Web/Desktop version 3.3.15 and prior to Notesnook iOS/Android version 3.3.20, a stored XSS vulnerability in the note export flow can be escalated to remote code execution in the desktop app. The root cause is that exported note fields such as title, headline, and content are inserted into the generated HTML template without HTML escaping. When the note is later exported to PDF, Notesnook renders that HTML into a same-origin, unsandboxed iframe using iframe.srcdoc = .... Injected script executes in the Notesnook origin. In the desktop app, this becomes RCE because Electron is configured with nodeIntegration: true and contextIsolation: false. This issue has been patched in Notesnook Web/Desktop version 3.3.15 and Notesnook iOS/Android version 3.3.20.
Published: 2026-05-04T16:43:07.527Z
Updated: 2026-05-05T03:56:38.973Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33976 |
vulnerable | 2026-06-08 07:59:11.648089 |
Notesnook vulnerable to RCE via stored XSS in Web Clipper rendering
CRITICAL (9.7)
Notesnook is a note-taking app. Prior to version 3.3.11 on Web/Desktop and 3.3.17 on Android/iOS, a stored XSS in the Web Clipper rendering flow can be escalated to remote code execution in the desktop app. The root cause is that the clipper preserves attacker-controlled attributes from the source page’s root element and stores them inside web-clip HTML. When the clip is later opened, Notesnook renders that HTML into a same-origin, unsandboxed iframe using `contentDocument.write(...)`. Event-handler attributes such as `onload`, `onclick`, or `onmouseover` execute in the Notesnook origin. In the desktop app, this becomes RCE because Electron is configured with `nodeIntegration: true` and `contextIsolation: false`. Version 3.3.11 Web/Desktop and 3.3.17 on Android/iOS patch the issue.
Published: 2026-03-27T21:26:10.127Z
Updated: 2026-04-03T03:55:22.486Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33955 |
vulnerable | 2026-06-08 07:59:11.638570 |
Notesnook vulnerable to RCE via stored XSS in Note History diff viewer
HIGH (8.6)
Notesnook is a note-taking app. Prior to version 3.3.11 on Web/Desktop, a cross-site scripting vulnerability stored in the note history comparison viewer can escalate to remote code execution in a desktop application. The issue is triggered when an attacker-controlled note header is displayed using `dangerouslySetInnerHTML` without secure handling. When combined with the full backup and restore feature in the desktop application, this becomes remote code execution because Electron is configured with `nodeIntegration: true` and `contextIsolation: false`. Version 3.3.11 patches the issue.
Published: 2026-03-27T21:27:31.554Z
Updated: 2026-04-03T13:02:56.898Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-31876 |
vulnerable | 2026-06-08 07:57:16.037675 |
Notesnook has Stored XSS via unsanitized Twitter/X embed URL in editor (`tweetToEmbed`)
MEDIUM (5.4)
Notesnook is a note-taking app focused on user privacy & ease of use. Prior to 3.3.9, a Stored Cross-Site Scripting (XSS) vulnerability existed in Notesnook's editor embed component when rendering Twitter/X embed URLs. The tweetToEmbed() function in component.tsx interpolated the user-supplied URL directly into an HTML string without escaping, which was then assigned to the srcdoc attribute of an <iframe>. This vulnerability is fixed in 3.3.9.
Published: 2026-03-11T18:17:08.142Z
Updated: 2026-03-12T20:08:12.048Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.