<?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>Sat, 10 Oct 2026 12:37:27 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-385235</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-385235</link>
      <description>EUVD-2026-385235</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-385235</guid>
    </item>
    <item>
      <title>fkie_cve-2026-108260</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-108260</link>
      <description>&lt;p&gt;Tina is a headless content management system. Prior to 0.2.1, the tina-markdown element in packages/@tinacms/web-components/src/tina-markdown.js assigns a rich-text node.url value directly to an anchor href without validating the URL scheme. A content author can store a link using a script-capable scheme, and a visitor who clicks the rendered link executes attacker-controlled script in the site&amp;#39;s origin. The script can access same-origin application data and, when the visitor is an editor or administrator, may expose credentials stored by the TinaCMS admin on that origin. This issue is fixed in version 0.2.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Tina is a headless content management system. Prior to 0.2.1, the tina-markdown element in packages/@tinacms/web-components/src/tina-markdown.js assigns a rich-text node.url value directly to an anchor href without validating the URL scheme. A content author can store a link using a script-capable scheme, and a visitor who clicks the rendered link executes attacker-controlled script in the site&amp;#39;s origin. The script can access same-origin application data and, when the visitor is an editor or administrator, may expose credentials stored by the TinaCMS admin on that origin. This issue is fixed in version 0.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-108260</guid>
    </item>
    <item>
      <title>GHSA-c42q-qvc3-j6vg — @tinacms/web-components: `tina-markdown` writes rich-text link URLs into `href` without scheme validation, allowing sto…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c42q-qvc3-j6vg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @tinacms/web-components&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`&amp;lt;tina-markdown&amp;gt;` renders a rich-text AST into the DOM and, for `a` nodes, assigns the node&amp;#39;s URL straight to the anchor&amp;#39;s `href` with no scheme check. A link authored in the CMS as `javascript:…` renders as a live `javascript:` anchor, so a visitor who clicks it executes attacker-supplied script in the site&amp;#39;s origin. Every sibling renderer in the repository already sanitizes these URLs; this one does not.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The unvalidated sink:&lt;/p&gt;
&lt;p&gt;```
packages/@tinacms/web-components/src/tina-markdown.js:67-69
  if (node.type === &amp;#39;html&amp;#39; || node.type === &amp;#39;html_inline&amp;#39;) {
    return DOMPurify.sanitize(node.value, { RETURN_DOM_FRAGMENT: true });
  }
packages/@tinacms/web-components/src/tina-markdown.js:75    if (node.url &amp;amp;&amp;amp; node.type === &amp;#39;a&amp;#39;) el.href = node.url;
packages/@tinacms/web-components/src/tina-markdown.js:76    if (node.url &amp;amp;&amp;amp; node.type === &amp;#39;img&amp;#39;) el.src = node.url;
```&lt;/p&gt;
&lt;p&gt;`node.url` comes from the `content` attribute the site populates from the TinaCMS content API (`:169-176`), i.e. whatever a content author typed into a rich-text field. The DOMPurify call at `:68` handles only raw-HTML node values and returns before the anchor branch, so it never inspects `node.url`. Line 75 is a direct property assignment — no HTML parser, no sanitizer. The `mode: &amp;#39;open&amp;#39;` shadow root (`:164-167`) provides no script isolation.&lt;/p&gt;
&lt;p&gt;The guard that exists in every sibling renderer:&lt;/p&gt;
&lt;p&gt;```
packages/@tinacms/mdx/src/sanitize-url.ts:10          allowedSchemes = [&amp;#39;http&amp;#39;,&amp;#39;https&amp;#39;,&amp;#39;mailto&amp;#39;,&amp;#39;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @tinacms/web-components&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`&amp;lt;tina-markdown&amp;gt;` renders a rich-text AST into the DOM and, for `a` nodes, assigns the node&amp;#39;s URL straight to the anchor&amp;#39;s `href` with no scheme check. A link authored in the CMS as `javascript:…` renders as a live `javascript:` anchor, so a visitor who clicks it executes attacker-supplied script in the site&amp;#39;s origin. Every sibling renderer in the repository already sanitizes these URLs; this one does not.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The unvalidated sink:&lt;/p&gt;
&lt;p&gt;```
packages/@tinacms/web-components/src/tina-markdown.js:67-69
  if (node.type === &amp;#39;html&amp;#39; || node.type === &amp;#39;html_inline&amp;#39;) {
    return DOMPurify.sanitize(node.value, { RETURN_DOM_FRAGMENT: true });
  }
packages/@tinacms/web-components/src/tina-markdown.js:75    if (node.url &amp;amp;&amp;amp; node.type === &amp;#39;a&amp;#39;) el.href = node.url;
packages/@tinacms/web-components/src/tina-markdown.js:76    if (node.url &amp;amp;&amp;amp; node.type === &amp;#39;img&amp;#39;) el.src = node.url;
```&lt;/p&gt;
&lt;p&gt;`node.url` comes from the `content` attribute the site populates from the TinaCMS content API (`:169-176`), i.e. whatever a content author typed into a rich-text field. The DOMPurify call at `:68` handles only raw-HTML node values and returns before the anchor branch, so it never inspects `node.url`. Line 75 is a direct property assignment — no HTML parser, no sanitizer. The `mode: &amp;#39;open&amp;#39;` shadow root (`:164-167`) provides no script isolation.&lt;/p&gt;
&lt;p&gt;The guard that exists in every sibling renderer:&lt;/p&gt;
&lt;p&gt;```
packages/@tinacms/mdx/src/sanitize-url.ts:10          allowedSchemes = [&amp;#39;http&amp;#39;,&amp;#39;https&amp;#39;,&amp;#39;mailto&amp;#39;,&amp;#39;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c42q-qvc3-j6vg</guid>
    </item>
  </channel>
</rss>
