Tiptap Core XSS via prototype pollution in attribute merging
- Exploited
- No known exploitation
- Fix
- Fixed in 3.30.4
- Who is exposed
- Not reported
Summary
The Tiptap @tiptap/core package has a cross-site scripting flaw. Untrusted JSON attribute data containing a `__proto__` key can alter a merged object's prototype, which lets injected event handlers run JavaScript when the content is rendered. An attacker can reach this remotely without logging in, but a user must take an action for the script to run.
Written by a model
Original description
Tiptap @tiptap/core 2.0.0-alpha.0 before 3.30.4 contains a cross-site scripting vulnerability that allows attackers to inject DOM attributes via a __proto__ key passed to mergeAttributes(). Attackers can supply untrusted JSON attribute data whose __proto__ replaces the merged object's prototype, causing DOMSerializer.renderSpec to render injected event handlers that execute JavaScript.
What to do
Upgrade to a fixed version: 3.30.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133170 (Tiptap @tiptap/core 2.0.0-alpha.0 before 3.30.4 XSS via mergeAttributes() Prototype Manipulation), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133170 (entry last updated 2026-11-19):
Affected:
- npm package @tiptap/core: from 2.0.0-alpha.0, fixed in 3.30.4
Fixed versions: 3.30.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133170 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133170 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ueberdosis/tiptap/security/advisories/GHSA-cp6q-959q-f8rh
- https://github.com/ueberdosis/tiptap/commit/01d7af8c983ee5954c63734f4fa46cb23ae3246d
- https://github.com/ueberdosis/tiptap/releases/tag/v3.30.4
- https://www.vulncheck.com/advisories/tiptap-tiptap-core-2.0.0-alpha.0-before-3.30.4-xss-via-mergeattributes-prototype-manipulation
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133170
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133170"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach20/20@tiptap/core: 37.3M downloads a week
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 84 if added to CISA KEV
- Would score about 79 if CISA's SSVC rates exploitation active
- Would score about 44 if advisories confirm default setups are exposed
Impact
- Widely used@tiptap/core has 37.3m weekly downloads. npmjs.com
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · ueberdosis/tiptap · Advisory GHSA-cp6q-959q-f8rh |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133170 |
| Record | NVD · CVE-2026-133170 |
| Other links 3 | |
| Patch | GitHub · ueberdosis/tiptap · Commit 01d7af8c |
| Repository | GitHub · ueberdosis/tiptap · Release v3.30.4 |
| Link | vulncheck.com · advisories/tiptap-tiptap-core-2.0.0-alpha.0-before-3.30.4-xss-via-mergeattributes-prototype-manipulation |
Questions about CVE-2026-133170
Is CVE-2026-133170 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133170?
@tiptap/core (npm): from 2.0.0-alpha.0 before 3.30.4.
Source: cve.now feed data
How do I fix CVE-2026-133170?
Upgrade to a fixed version: 3.30.4.
Source: cve.now feed data
Related
- CVE-2026-133171Tiptap @tiptap/core 3.7.0 before 3.30.5 ReDoS via Markdown Attribute Parsing
- CVE-2026-47110Tiptap for PHP < 2.1.1 DoS via Malformed href Attribute
- CVE-2026-133243node-soap before 1.14.1 Prototype Pollution via multiRef id in WSDL.xmlToObject
- CVE-2026-114604GraphQL Tools: Prototype pollution in mergeIncrementalResult via non-primitive path segments
- CVE-2026-128337ExcelJS through 4.4.0 Prototype Pollution via x14 Conditional Formatting Rule ID
- CVE-2026-125117Mongoose walks into inherited properties when hydrating, setting, and merging, allowing overwrites of built-in functions (denial of…
No corrections so far. Something wrong on this page? Report an error.