CVE-2026-73427

LOWPre-NVD 2.12.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (45th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 2.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Trix is a what-you-see-is-what-you-get rich text editor for everyday writing. Prior to 2.1.18, Trix is vulnerable to cross-site scripting when a crafted application/x-trix-document JSON payload is dropped into an editor using the fallback Level0InputController, such as an embedded WebView without Input Events Level 2 support. The StringPiece.fromJSON method trusts href attributes from the JSON payload without sanitization, allowing a draggable element containing a javascript: URI to bypass DOMPurify sanitization and inject executable JavaScript into the DOM. Exploitation requires the victim to drag and drop attacker-controlled content, and server-side HTML sanitization can neutralize the payload on save. This issue is fixed in version 2.1.18.

CVSS v3
2.1
EG Score
2.1LOWmedium confidence
EG Risk
10
EG Risk 10/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity21% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 12, 2026

Last Modified

September 9, 2026

References (4)

Vendor Advisories for CVE-2026-73427(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
trix—
  • every version up to 2.1.18: fixed in 2.1.18
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
action_text-trix0.0.1, 2.1.15, 2.1.16, 2.1.17
  • every version up to 2.1.18: fixed in 2.1.18
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-06 17:39 UTCEG score recompute
  2. 2026-10-06 15:18 UTCEPSS rescore
  3. 2026-10-05 17:43 UTCEPSS rescore
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-03 19:55 UTCEG score recompute
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-01 19:50 UTCEPSS rescore
  8. 2026-09-30 21:52 UTCEG score recompute
  9. 2026-09-29 15:24 UTCEPSS rescore
  10. 2026-09-28 13:52 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-27 09:51 UTCEG score recompute
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-24 10:26 UTCEG score recompute
  15. 2026-09-21 21:09 UTCEPSS rescore
  16. 2026-09-21 12:41 UTCEG score recompute
  17. 2026-09-20 20:16 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 14:43 UTCEG score recompute
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-15 16:59 UTCEG score recompute
  23. 2026-09-15 03:12 UTCEPSS rescore
  24. 2026-09-12 19:13 UTCEG score recompute
  25. 2026-09-12 15:02 UTCEPSS rescore
Show 42 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-09 05:10 UTCEG score recompute
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-06 13:48 UTCEPSS rescore
  6. 2026-09-05 21:44 UTCEG score recompute
  7. 2026-09-04 05:07 UTCEPSS rescore
  8. 2026-09-02 23:57 UTCEG score recompute
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-09-01 04:40 UTCEPSS rescore
  13. 2026-08-31 02:12 UTCEG score recompute
  14. 2026-08-30 19:18 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:42 UTCEPSS rescore
  18. 2026-08-28 04:28 UTCEG score recompute
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:47 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 06:36 UTCEG score recompute
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-22 08:40 UTCEG score recompute
  25. 2026-08-21 23:49 UTCEPSS rescore
  26. 2026-08-20 22:56 UTCEPSS rescore
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-19 10:55 UTCEG score recompute
  29. 2026-08-18 13:49 UTCEPSS rescore
  30. 2026-08-18 13:49 UTCEPSS rescore
  31. 2026-08-17 13:47 UTCEPSS rescore
  32. 2026-08-16 14:56 UTCEPSS rescore
  33. 2026-08-16 14:56 UTCEPSS rescore
  34. 2026-08-16 13:11 UTCEG score recompute
  35. 2026-08-16 02:15 UTCEPSS rescore
  36. 2026-08-15 01:31 UTCEPSS rescore
  37. 2026-08-13 22:00 UTCEPSS rescore
  38. 2026-08-13 15:26 UTCEG score recompute
  39. 2026-08-13 14:24 UTCEG score recompute
  40. 2026-08-12 21:20 UTCEG score recompute
  41. 2026-08-12 21:01 UTCEG score recompute
  42. 2026-08-12 21:00 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-73427?
CVE-2026-73427 is a low vulnerability published on August 12, 2026. Trix is a what-you-see-is-what-you-get rich text editor for everyday writing. Prior to 2.1.18, Trix is vulnerable to cross-site scripting when a crafted application/x-trix-document JSON payload is dropped into an editor using the fallback Level0InputController, such as an embedded WebView without…
When was CVE-2026-73427 disclosed?
CVE-2026-73427 was first published on August 12, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73427 actively exploited?
CVE-2026-73427 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73427?
CVE-2026-73427 has a CVSS base score of 2.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73427?
A fix for CVE-2026-73427 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73427 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73427

Explore →

Is Your Infrastructure Affected by CVE-2026-73427?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs