Cross-Site Scripting (XSS) in trix (CVE-2026-73427)
Summary
Cross-site scripting in trix (CVE-2026-73427). Risk of unauthorized operations or information disclosure. Exploitable via StringPiece.fromJSON. Mitigation: upgrade to 2.1.18 or later.
Original description
The description as published by the source.
Impact
The Trix editor, in versions prior to 2.1.18, is vulnerable to XSS when a crafted application/x-trix-document JSON payload is dropped into the editor in environments using the fallback Level0InputController (e.g., embedded WebViews lacking Input Events Level 2 support).
The StringPiece.fromJSON method trusted href attributes from the JSON payload without sanitization. An attacker could craft a draggable element containing a javascript: URI in the href attribute that, when dropped into a vulnerable editor, would bypass DOMPurify sanitization and inject executable JavaScript into the DOM.
Exploitation requires a specific environment (Level0InputController fallback) and social engineering (victim must drag and drop attacker-controlled content into the editor). Applications using server-side HTML sanitization (such as Rails' built-in sanitizer) are additionally protected, as the payload is neutralized on save.
Patches
Update Recommendation: Users should upgrade to Trix editor version 2.1.18 or later.
References
The XSS vulnerability was responsibly reported by Hackerone researcher newbiefromcoma.
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-73427 has been found in trix.
Attackers can target a specific entry point like StringPiece.fromJSON over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade trix to 2.1.18 or later.
If unsure, ask your IT team or search "trix CVE-2026-73427" on the vendor's site.
CVE-2026-73427 (trix) — CWE-79
Attack surface: StringPiece.fromJSON / href
Patched: 2.1.18 — 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.
Cross-site scripting (XSS) (CWE-79) exists in trix. Attackers reach the vulnerable code path via StringPiece.fromJSON.
Check the vendor advisory for the affected versions of trix. Attack surface: StringPiece.fromJSON / href.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.1.18.
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 'trix' . 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 'trix' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
trixを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade trix to 2.1.18ステージング環境で 2.1.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。