Vulnerability in ueberdosis/tiptap-php (CVE-2026-47110)
Summary
Vulnerability in ueberdosis/tiptap-php (CVE-2026-47110). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.1.1 or later.
Original description
The description as published by the source.
Tiptap for PHP before version 2.1.1 contains an input validation vulnerability that allows authenticated attackers to cause a denial of service by submitting Tiptap JSON with the attrs.href field set to an array instead of a string, causing an unhandled TypeError in the Link::isAllowedUri() function when passed to preg_match(). Attackers can persist malformed JSON records that permanently crash the server-side HTML rendering pipeline for all subsequent viewers of that record until the database entry is manually repaired.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47110 has been found in ueberdosis/tiptap-php.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade ueberdosis/tiptap-php to 2.1.1 or later.
If unsure, ask your IT team or search "ueberdosis/tiptap-php CVE-2026-47110" on the vendor's site.
CVE-2026-47110 (ueberdosis/tiptap-php) — CWE-241 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-241) exists in ueberdosis/tiptap-php.
Check the vendor advisory for the affected versions of ueberdosis/tiptap-php.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ueberdosis/tiptap-php' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ueberdosis/tiptap-php' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ueberdosis/tiptap-phpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ueberdosis/tiptap-php to 2.1.1ステージング環境で 2.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web vulncheck.com
- web github.com