<?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>Sun, 18 Oct 2026 06:01:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-178195</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-178195</link>
      <description>EUVD-2026-178195</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-178195</guid>
    </item>
    <item>
      <title>fkie_cve-2022-25863</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-25863</link>
      <description>&lt;p&gt;The package gatsby-plugin-mdx before 2.14.1, from 3.0.0 and before 3.15.2 are vulnerable to Deserialization of Untrusted Data when passing input through to the gray-matter package, due to its default configurations that are missing input sanitization. Exploiting this vulnerability is possible when passing input in both webpack (MDX files in src/pages or MDX file imported as a component in frontend / React code) and data mode (querying MDX nodes via GraphQL). Workaround: If an older version of gatsby-plugin-mdx must be used, input passed into the plugin should be sanitized ahead of processing.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The package gatsby-plugin-mdx before 2.14.1, from 3.0.0 and before 3.15.2 are vulnerable to Deserialization of Untrusted Data when passing input through to the gray-matter package, due to its default configurations that are missing input sanitization. Exploiting this vulnerability is possible when passing input in both webpack (MDX files in src/pages or MDX file imported as a component in frontend / React code) and data mode (querying MDX nodes via GraphQL). Workaround: If an older version of gatsby-plugin-mdx must be used, input passed into the plugin should be sanitized ahead of processing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-25863</guid>
    </item>
    <item>
      <title>GHSA-mj46-r4gr-5x83 — Unsanitized JavaScript code injection possible in gatsby-plugin-mdx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mj46-r4gr-5x83</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: gatsby-plugin-mdx&lt;/p&gt;
&lt;p&gt;### Impact
The gatsby-plugin-mdx plugin prior to versions 3.15.2 and 2.14.1 passes input through to the `gray-matter` npm package, which is vulnerable to JavaScript injection in its default configuration, unless input is sanitized.  The vulnerability is present when passing input in both webpack (MDX files in `src/pages` or MDX file imported as component in frontend / React code) and data mode (querying MDX nodes via GraphQL).  Injected JavaScript executes in the context of the build server.&lt;/p&gt;
&lt;p&gt;To exploit this vulnerability untrusted/unsanitized input would need to be sourced or added into an MDX file.  The following MDX payload demonstrates a vulnerable configuration:
```
---js
((require(&amp;#34;child_process&amp;#34;)).execSync(&amp;#34;id &amp;gt;&amp;gt; /tmp/rce&amp;#34;))
--- 
```&lt;/p&gt;
&lt;p&gt;### Patches
A patch has been introduced in `gatsby-plugin-mdx@3.15.2` and `gatsby-plugin-mdx@2.14.1` which mitigates the issue by disabling the `gray-matter` JavaScript Frontmatter engine.  The patch introduces a new option, `JSFrontmatterEngine` which is set to `false` by default.  When setting `JSFrontmatterEngine` to `true`, input passed to `gatsby-plugin-mdx` must be sanitized before processing to avoid a security risk.  Warnings are displayed when enabling `JSFrontmatterEngine` to `true` or if it appears that the MDX input is attempting to use the Frontmatter engine.&lt;/p&gt;
&lt;p&gt;### Workarounds
If an older version of `gatsby-plugin-mdx` must be used, input passed into the plugin should be sanitized ahead of processing.&lt;/p&gt;
&lt;p&gt;**We encourage projects…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: gatsby-plugin-mdx&lt;/p&gt;
&lt;p&gt;### Impact
The gatsby-plugin-mdx plugin prior to versions 3.15.2 and 2.14.1 passes input through to the `gray-matter` npm package, which is vulnerable to JavaScript injection in its default configuration, unless input is sanitized.  The vulnerability is present when passing input in both webpack (MDX files in `src/pages` or MDX file imported as component in frontend / React code) and data mode (querying MDX nodes via GraphQL).  Injected JavaScript executes in the context of the build server.&lt;/p&gt;
&lt;p&gt;To exploit this vulnerability untrusted/unsanitized input would need to be sourced or added into an MDX file.  The following MDX payload demonstrates a vulnerable configuration:
```
---js
((require(&amp;#34;child_process&amp;#34;)).execSync(&amp;#34;id &amp;gt;&amp;gt; /tmp/rce&amp;#34;))
--- 
```&lt;/p&gt;
&lt;p&gt;### Patches
A patch has been introduced in `gatsby-plugin-mdx@3.15.2` and `gatsby-plugin-mdx@2.14.1` which mitigates the issue by disabling the `gray-matter` JavaScript Frontmatter engine.  The patch introduces a new option, `JSFrontmatterEngine` which is set to `false` by default.  When setting `JSFrontmatterEngine` to `true`, input passed to `gatsby-plugin-mdx` must be sanitized before processing to avoid a security risk.  Warnings are displayed when enabling `JSFrontmatterEngine` to `true` or if it appears that the MDX input is attempting to use the Frontmatter engine.&lt;/p&gt;
&lt;p&gt;### Workarounds
If an older version of `gatsby-plugin-mdx` must be used, input passed into the plugin should be sanitized ahead of processing.&lt;/p&gt;
&lt;p&gt;**We encourage projects…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mj46-r4gr-5x83</guid>
    </item>
    <item>
      <title>gsd-2022-25863</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-25863</link>
      <description>gsd-2022-25863</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-25863</guid>
    </item>
  </channel>
</rss>
