<?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>Wed, 07 Oct 2026 13:27:11 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-264051</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-264051</link>
      <description>EUVD-2026-264051</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-264051</guid>
    </item>
    <item>
      <title>fkie_cve-2025-68278</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-68278</link>
      <description>&lt;p&gt;Tina is a headless content management system. In tinacms prior to version 3.1.1, tinacms uses the gray-matter package in an insecure way allowing attackers that can control the content of the processed markdown files, e.g., blog posts, to execute arbitrary code. tinacms version 3.1.1, @tinacms/cli version 2.0.4, and @tinacms/graphql version 2.0.3 contain a fix for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Tina is a headless content management system. In tinacms prior to version 3.1.1, tinacms uses the gray-matter package in an insecure way allowing attackers that can control the content of the processed markdown files, e.g., blog posts, to execute arbitrary code. tinacms version 3.1.1, @tinacms/cli version 2.0.4, and @tinacms/graphql version 2.0.3 contain a fix for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-68278</guid>
    </item>
    <item>
      <title>GHSA-529f-9qwm-9628 — tinacms is vulnerable to arbitrary code execution</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-529f-9qwm-9628</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: tinacms, npm: @tinacms/cli, npm: @tinacms/graphql&lt;/p&gt;
&lt;p&gt;### Summary
```tinacms``` uses the ```gray-matter``` package in an insecure way allowing attackers that can control the content of the processed markdown files, e.g., blog posts, to execute arbitrary code.&lt;/p&gt;
&lt;p&gt;### Details
The ```gray-matter``` package executes by default the code in the markdown file&amp;#39;s front matter. ```tinacms``` does not change this behavior when process markdown file, e.g., by passing a custom engine property for js/javascript in the options object.&lt;/p&gt;
&lt;p&gt;### PoC
1. Create a tinacms app using the cli/documentation: 
```
npx create-tina-app@latest
```
2. Modify one of the blog posts to contain the following front matter:
```js
---js
{
  &amp;#34;title&amp;#34;: &amp;#34;Pawned&amp;#34; + console.log(require(&amp;#34;fs&amp;#34;).readFileSync(&amp;#34;/etc/passwd&amp;#34;).toString())
}
---
```
3. Start the tinacms server, e.g., with ```npm run dev```
4. Observe the console of the server printing the password file, showing that attackers can execute arbitrary commands.&lt;/p&gt;
&lt;p&gt;### Impact
RCE: attackers can execute arbitrary JavaScript code on the server hosting tinacms.&lt;/p&gt;
&lt;p&gt;### Feasibility
Potential attack scenarios can be executed like this: Companies often have technical writers as contractors. These contractors produce md files, which they send over email or upload in a shared cloud folder. Developers download these files and upload them in ```tinacms```&amp;#39;s content folder. While this example might appear speculative or contrived, a general observation is that developers would be very surprised to find out that processing untrusted mark…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: tinacms, npm: @tinacms/cli, npm: @tinacms/graphql&lt;/p&gt;
&lt;p&gt;### Summary
```tinacms``` uses the ```gray-matter``` package in an insecure way allowing attackers that can control the content of the processed markdown files, e.g., blog posts, to execute arbitrary code.&lt;/p&gt;
&lt;p&gt;### Details
The ```gray-matter``` package executes by default the code in the markdown file&amp;#39;s front matter. ```tinacms``` does not change this behavior when process markdown file, e.g., by passing a custom engine property for js/javascript in the options object.&lt;/p&gt;
&lt;p&gt;### PoC
1. Create a tinacms app using the cli/documentation: 
```
npx create-tina-app@latest
```
2. Modify one of the blog posts to contain the following front matter:
```js
---js
{
  &amp;#34;title&amp;#34;: &amp;#34;Pawned&amp;#34; + console.log(require(&amp;#34;fs&amp;#34;).readFileSync(&amp;#34;/etc/passwd&amp;#34;).toString())
}
---
```
3. Start the tinacms server, e.g., with ```npm run dev```
4. Observe the console of the server printing the password file, showing that attackers can execute arbitrary commands.&lt;/p&gt;
&lt;p&gt;### Impact
RCE: attackers can execute arbitrary JavaScript code on the server hosting tinacms.&lt;/p&gt;
&lt;p&gt;### Feasibility
Potential attack scenarios can be executed like this: Companies often have technical writers as contractors. These contractors produce md files, which they send over email or upload in a shared cloud folder. Developers download these files and upload them in ```tinacms```&amp;#39;s content folder. While this example might appear speculative or contrived, a general observation is that developers would be very surprised to find out that processing untrusted mark…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-529f-9qwm-9628</guid>
    </item>
  </channel>
</rss>
