<?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>Tue, 06 Oct 2026 23:31:38 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-00243</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-00243</link>
      <description>bdu:2026-00243</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-00243</guid>
    </item>
    <item>
      <title>EUVD-2026-254434</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-254434</link>
      <description>EUVD-2026-254434</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-254434</guid>
    </item>
    <item>
      <title>fkie_cve-2025-53967</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-53967</link>
      <description>&lt;p&gt;Framelink Figma MCP Server before 0.6.3 allows an unauthenticated remote attacker to execute arbitrary operating system commands via a crafted HTTP POST request with shell metacharacters in input that is used by a fetchWithRetry curl command. The vulnerable endpoint fails to properly sanitize user-supplied input, enabling the attacker to inject malicious commands that are executed with the privileges of the MCP process. Exploitation requires network access to the MCP interface.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Framelink Figma MCP Server before 0.6.3 allows an unauthenticated remote attacker to execute arbitrary operating system commands via a crafted HTTP POST request with shell metacharacters in input that is used by a fetchWithRetry curl command. The vulnerable endpoint fails to properly sanitize user-supplied input, enabling the attacker to inject malicious commands that are executed with the privileges of the MCP process. Exploitation requires network access to the MCP interface.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-53967</guid>
    </item>
    <item>
      <title>GHSA-gxw4-4fc5-9gr5 — figma-developer-mcp vulnerable to command injection in get_figma_data tool</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gxw4-4fc5-9gr5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: figma-developer-mcp&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A command injection vulnerability exists in the `figma-developer-mcp` MCP Server. The vulnerability is caused by the unsanitized use of input parameters within a call to `child_process.exec`, enabling an attacker to inject arbitrary system commands. Successful exploitation can lead to remote code execution under the server process&amp;#39;s privileges.&lt;/p&gt;
&lt;p&gt;The server constructs and executes shell commands using unvalidated user input directly within command-line strings. This introduces the possibility of shell metacharacter injection (`|`, `&amp;gt;`, `&amp;amp;&amp;amp;`, etc.).&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The MCP Server exposes tools to perform several figma operations.  An MCP Client can be instructed to execute additional actions for example via indirect prompt injection that can lead to command injection by calling vulnerable tools with malicious inputs. Below some example of vulnerable code and different ways to test this vulnerability.&lt;/p&gt;
&lt;p&gt;### Vulnerable code&lt;/p&gt;
&lt;p&gt;The following snippet illustrates the vulnerable code pattern used in the MCP Server’s tooling. 
```js
// https://github.com/GLips/Figma-Context-MCP/blob/v0.5.2/src/utils/fetch-with-retry.ts#L35&lt;/p&gt;
&lt;p&gt;export async function fetchWithRetry&amp;lt;T&amp;gt;(url: string, options: RequestOptions = {}): Promise&amp;lt;T&amp;gt; {
  try {
    const response = await fetch(url, options);
    ...
  } catch (fetchError: any) {
	...
    const curlHeaders = formatHeadersForCurl(options.headers);
    ...
    const curlCommand = `curl -s -S --fail-with-body -L ${curlHeaders.join(&amp;#34; &amp;#34;)} &amp;#34;${url}&amp;#34;`…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: figma-developer-mcp&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A command injection vulnerability exists in the `figma-developer-mcp` MCP Server. The vulnerability is caused by the unsanitized use of input parameters within a call to `child_process.exec`, enabling an attacker to inject arbitrary system commands. Successful exploitation can lead to remote code execution under the server process&amp;#39;s privileges.&lt;/p&gt;
&lt;p&gt;The server constructs and executes shell commands using unvalidated user input directly within command-line strings. This introduces the possibility of shell metacharacter injection (`|`, `&amp;gt;`, `&amp;amp;&amp;amp;`, etc.).&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The MCP Server exposes tools to perform several figma operations.  An MCP Client can be instructed to execute additional actions for example via indirect prompt injection that can lead to command injection by calling vulnerable tools with malicious inputs. Below some example of vulnerable code and different ways to test this vulnerability.&lt;/p&gt;
&lt;p&gt;### Vulnerable code&lt;/p&gt;
&lt;p&gt;The following snippet illustrates the vulnerable code pattern used in the MCP Server’s tooling. 
```js
// https://github.com/GLips/Figma-Context-MCP/blob/v0.5.2/src/utils/fetch-with-retry.ts#L35&lt;/p&gt;
&lt;p&gt;export async function fetchWithRetry&amp;lt;T&amp;gt;(url: string, options: RequestOptions = {}): Promise&amp;lt;T&amp;gt; {
  try {
    const response = await fetch(url, options);
    ...
  } catch (fetchError: any) {
	...
    const curlHeaders = formatHeadersForCurl(options.headers);
    ...
    const curlCommand = `curl -s -S --fail-with-body -L ${curlHeaders.join(&amp;#34; &amp;#34;)} &amp;#34;${url}&amp;#34;`…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gxw4-4fc5-9gr5</guid>
    </item>
  </channel>
</rss>
