Skip to content

[5.x] Allow ueberdosis/tiptap-php ^2.1.2 - #15620

Merged
jasonvarga merged 1 commit into
5.xfrom
5.x-tiptap-2
Oct 8, 2026
Merged

jasonvarga merged 1 commit into
5.xfrom
5.x-tiptap-2

Conversation

@jasonvarga

Copy link
Copy Markdown
Member

GitHub reviewed GHSA-4595-7fjw-r3jh (CVE-2026-47110) on 2026-10-07, attaching ueberdosis/tiptap-php < 2.1.1. Composer 2.9+ blocks those versions by default, so on 5.x a full composer update (or composer update statamic/cms -W) now fails.

This widens the constraint to ^1.4 || ^2.1.2. Composer will pick 2.x by default, while sites that already have 1.4 locked, or that ignore the advisory, can stay on it. The minimum is 2.1.2 rather than 2.1.1 because 2.1.1 still crashes on other non-scalar attributes.

To keep output the same on 2.x:

  • LinkMark gets the allowedProtocols/isAllowedUri options from [6.x] Update ueberdosis/tiptap-php to ^2.0 #12050, so v2's link sanitizer doesn't strip statamic://, entry:: and asset:: links.
  • A custom Strike mark keeps rendering <strike>, since v2 renders <s>.

Also brings over the GraphQL test fixture fix from #13678 (v2 no longer wraps a top-level text node in <p>) and adds a test for strike output.

The advisory isn't meaningfully exploitable in Statamic, since only control panel users can author Bard content. The test suite passes on both tiptap-php 1.4.0 and 2.2.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jasonvarga
jasonvarga merged commit 0700a08 into 5.x Oct 8, 2026
14 checks passed
@jasonvarga
jasonvarga deleted the 5.x-tiptap-2 branch October 8, 2026 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant