NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm💎 RubyGems
Not in CISA KEV
MEDIUM severity

Trix has a stored XSS vulnerability through its attachment attributeGHSA-g9jg-w8vm-g96v

MEDIUMFix: basecamp/trix@73c20cf

GHSA-g9jg-w8vm-g96v is a medium-severity (CVSS 4.6) vulnerability in trix. A fix is available for trix — see the affected versions and patch details below.

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

66other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
trixnpm
725Kdownloads / week

Description

Impact

The Trix editor, in versions prior to 2.1.16, is vulnerable to XSS attacks through attachment payloads.

An attacker could inject malicious code into a data-trix-attachment attribute that, when rendered as HTML and clicked on, could execute arbitrary JavaScript code within the context of the user's session, potentially leading to unauthorized actions being performed or sensitive information being disclosed.

Patches

Update Recommendation: Users should upgrade to Trix editor version 2.1.16 or later.

Resources

The XSS vulnerability was reported by HackerOne researcher michaelcheers.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmtrixall versions2.1.16npm install trix@2.1.16
💎RubyGemsaction_text-trixall versions2.1.16bundle update action_text-trix --conservative

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update trix to 2.1.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g9jg-w8vm-g96v is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact The Trix editor, in versions prior to 2.1.16, is vulnerable to XSS attacks through attachment payloads. An attacker could inject malicious code into a data-trix-attachment attribute that, when rendered as HTML and clicked on, could execute arbitrary JavaScript code within the context of the user's session, potentially leading to unauthorized actions being performed or sensitive information being disclosed. ### Patches Update Recommendation: Users should upgrade to Trix editor version 2.1.16 or later. ### Resources The XSS vulnerability was reported by HackerOne researcher [michae
O3 Security · Impact-Aware SCA

Is GHSA-g9jg-w8vm-g96v in your dependencies?

Find it across npm, RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works
Trix has a stored XSS vulnerability through its attachment…