Cross-Site Scripting (XSS) in action_text-trix (CVE-2026-73426)
Summary
Cross-site scripting in action_text-trix (CVE-2026-73426). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.1.17 or later.
Original description
The description as published by the source.
Trix is a what-you-see-is-what-you-get rich text editor for everyday writing. Prior to 2.1.17, Trix is vulnerable to cross-site scripting when a data-trix-serialized-attributes attribute bypasses the DOMPurify sanitizer. An attacker can craft HTML containing a data-trix-serialized-attributes attribute with a malicious payload that, when rendered, executes arbitrary JavaScript in the user's session and may perform unauthorized actions or disclose sensitive information. This issue is fixed in version 2.1.17.
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-73426 has been found in action_text-trix.
Risk of unauthorized operations or information disclosure. CVSS score: 4.6/10.
What to do: upgrade action_text-trix to 2.1.17 or later.
If unsure, ask your IT team or search "action_text-trix CVE-2026-73426" on the vendor's site.
CVE-2026-73426 (action_text-trix) — CWE-79 / CVSS v3 4.6
Attack vector: remote (network-reachable)
Patched: 2.1.17 — 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 action_text-trix.
Check the vendor advisory for the affected versions of action_text-trix.
Severity: Medium (CVSS 4.6/10). Risk of unauthorized operations or information disclosure.
Update to 2.1.17.
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 'action_text-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 'action_text-trix' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
action_text-trixを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade action_text-trix to 2.1.17ステージング環境で 2.1.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com