<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 11:15:58 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-158679</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-158679</link>
      <description>EUVD-2026-158679</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-158679</guid>
    </item>
    <item>
      <title>fkie_cve-2024-43368</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-43368</link>
      <description>&lt;p&gt;The Trix editor, versions prior to 2.1.4, is vulnerable to XSS when pasting malicious code. This vulnerability is a bypass of the fix put in place for GHSA-qjqp-xr96-cj99. In pull request 1149, sanitation was added for Trix attachments with a `text/html` content type. However, Trix only checks the content type on the paste event&amp;#39;s `dataTransfer` object. As long as the `dataTransfer` has a content type of `text/html`, Trix parses its contents and creates an `Attachment` with them, even if the attachment itself doesn&amp;#39;t have a `text/html` content type. Trix then uses the attachment content to set the attachment element&amp;#39;s `innerHTML`. An attacker could trick a user to copy and paste malicious code that would execute arbitrary JavaScript code within the context of the user&amp;#39;s session, potentially leading to unauthorized actions being performed or sensitive information being disclosed. This vulnerability was fixed in version 2.1.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Trix editor, versions prior to 2.1.4, is vulnerable to XSS when pasting malicious code. This vulnerability is a bypass of the fix put in place for GHSA-qjqp-xr96-cj99. In pull request 1149, sanitation was added for Trix attachments with a `text/html` content type. However, Trix only checks the content type on the paste event&amp;#39;s `dataTransfer` object. As long as the `dataTransfer` has a content type of `text/html`, Trix parses its contents and creates an `Attachment` with them, even if the attachment itself doesn&amp;#39;t have a `text/html` content type. Trix then uses the attachment content to set the attachment element&amp;#39;s `innerHTML`. An attacker could trick a user to copy and paste malicious code that would execute arbitrary JavaScript code within the context of the user&amp;#39;s session, potentially leading to unauthorized actions being performed or sensitive information being disclosed. This vulnerability was fixed in version 2.1.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-43368</guid>
    </item>
    <item>
      <title>GHSA-qm2q-9f3q-2vcv — Trix has a cross-site Scripting vulnerability on copy &amp; paste</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qm2q-9f3q-2vcv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: trix&lt;/p&gt;
&lt;p&gt;The Trix editor, versions prior to 2.1.4, is vulnerable to XSS when pasting malicious code. This vulnerability is a bypass of the fix put in place for https://github.com/basecamp/trix/security/advisories/GHSA-qjqp-xr96-cj99. In https://github.com/basecamp/trix/pull/1149, we added sanitation for Trix attachments with a `text/html` content type. However, Trix only checks the content type on the paste event&amp;#39;s `dataTransfer` object. As long as the `dataTransfer` has a content type of `text/html`, Trix parses its contents and creates an `Attachment` with them, even if the attachment itself doesn&amp;#39;t have a `text/html` content type. Trix then uses the attachment content to set the attachment element&amp;#39;s `innerHTML`.&lt;/p&gt;
&lt;p&gt;### Impact
An attacker could trick a user to copy and paste malicious code that would execute arbitrary JavaScript code within the context of the user&amp;#39;s session, potentially leading to unauthorized actions being performed or sensitive information being disclosed.&lt;/p&gt;
&lt;p&gt;### Patches
**Update Recommendation:** Users should upgrade to Trix editor version 2.1.4 or later, which incorporates proper sanitization of input from copied content.&lt;/p&gt;
&lt;p&gt;### Workarounds
This is not really a workaround but something that should be considered in addition to upgrading to the patched version. If affected users can disallow browsers that don&amp;#39;t support a Content Security Policy, then this would be an effective workaround for this and all XSS vulnerabilities. Set CSP policies such as `script-src &amp;#39;self&amp;#39;`…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: trix&lt;/p&gt;
&lt;p&gt;The Trix editor, versions prior to 2.1.4, is vulnerable to XSS when pasting malicious code. This vulnerability is a bypass of the fix put in place for https://github.com/basecamp/trix/security/advisories/GHSA-qjqp-xr96-cj99. In https://github.com/basecamp/trix/pull/1149, we added sanitation for Trix attachments with a `text/html` content type. However, Trix only checks the content type on the paste event&amp;#39;s `dataTransfer` object. As long as the `dataTransfer` has a content type of `text/html`, Trix parses its contents and creates an `Attachment` with them, even if the attachment itself doesn&amp;#39;t have a `text/html` content type. Trix then uses the attachment content to set the attachment element&amp;#39;s `innerHTML`.&lt;/p&gt;
&lt;p&gt;### Impact
An attacker could trick a user to copy and paste malicious code that would execute arbitrary JavaScript code within the context of the user&amp;#39;s session, potentially leading to unauthorized actions being performed or sensitive information being disclosed.&lt;/p&gt;
&lt;p&gt;### Patches
**Update Recommendation:** Users should upgrade to Trix editor version 2.1.4 or later, which incorporates proper sanitization of input from copied content.&lt;/p&gt;
&lt;p&gt;### Workarounds
This is not really a workaround but something that should be considered in addition to upgrading to the patched version. If affected users can disallow browsers that don&amp;#39;t support a Content Security Policy, then this would be an effective workaround for this and all XSS vulnerabilities. Set CSP policies such as `script-src &amp;#39;self&amp;#39;`…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qm2q-9f3q-2vcv</guid>
    </item>
  </channel>
</rss>
