<?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 10:01:45 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-281064</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-281064</link>
      <description>EUVD-2026-281064</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-281064</guid>
    </item>
    <item>
      <title>fkie_cve-2026-35394</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-35394</link>
      <description>&lt;p&gt;Mobile Next is an MCP server for mobile development and automation. Prior to 0.0.50, the mobile_open_url tool in mobile-mcp passes user-supplied URLs directly to Android&amp;#39;s intent system without any scheme validation, allowing execution of arbitrary Android intents, including USSD codes, phone calls, SMS messages, and content provider access. This vulnerability is fixed in 0.0.50.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Mobile Next is an MCP server for mobile development and automation. Prior to 0.0.50, the mobile_open_url tool in mobile-mcp passes user-supplied URLs directly to Android&amp;#39;s intent system without any scheme validation, allowing execution of arbitrary Android intents, including USSD codes, phone calls, SMS messages, and content provider access. This vulnerability is fixed in 0.0.50.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-35394</guid>
    </item>
    <item>
      <title>GHSA-5qhv-x9j4-c3vm — @mobilenext/mobile-mcp: Arbitrary Android Intent Execution via mobile_open_url</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5qhv-x9j4-c3vm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @mobilenext/mobile-mcp&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `mobile_open_url` tool in mobile-mcp passes user-supplied URLs directly to Android&amp;#39;s intent system without any scheme validation, allowing execution of arbitrary Android intents, including USSD codes, phone calls, SMS messages, and content provider access.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerable code passes URLs directly to `adb shell am start -a android.intent.action.VIEW -d &amp;lt;url&amp;gt;` without checking the URL scheme. This can enable malicious schemes such as `tel:`, `sms:`, `mailto:`, `content://`, and `market://` to be executed.&lt;/p&gt;
&lt;p&gt;Since MCP servers are designed to be operated by AI agents, which are vulnerable to prompt injection attacks, a malicious document or website could inject instructions that cause the AI to execute dangerous intents on a connected mobile device.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker via prompt injection can:
- Execute USSD codes (e.g., `tel:*#06#` to display IMEI - confirmed on Pixel 7a, behavior varies by device; or device-specific factory reset codes)
- Initiate phone calls to premium rate numbers
- Draft SMS messages with attacker-controlled content
- Access content providers (contacts, SMS, call logs)
- Open app installation prompts&lt;/p&gt;
&lt;p&gt;### Proof of Concept
```json
{&amp;#34;jsonrpc&amp;#34;:&amp;#34;2.0&amp;#34;,&amp;#34;id&amp;#34;:1,&amp;#34;method&amp;#34;:&amp;#34;tools/call&amp;#34;,&amp;#34;params&amp;#34;:{&amp;#34;name&amp;#34;:&amp;#34;mobile_open_url&amp;#34;,&amp;#34;arguments&amp;#34;:{&amp;#34;device&amp;#34;:&amp;#34;&amp;lt;id&amp;gt;&amp;#34;,&amp;#34;url&amp;#34;:&amp;#34;tel:*#06#&amp;#34;}}}
```&lt;/p&gt;
&lt;p&gt;Result: IMEI displayed on device.
```json
{&amp;#34;jsonrpc&amp;#34;:&amp;#34;2.0&amp;#34;,&amp;#34;id&amp;#34;:1,&amp;#34;method&amp;#34;:&amp;#34;tools/call&amp;#34;,&amp;#34;params&amp;#34;:{&amp;#34;name&amp;#34;:&amp;#34;mobile_open_url&amp;#34;,&amp;#34;arguments&amp;#34;:{&amp;#34;device&amp;#34;:&amp;#34;&amp;lt;id&amp;gt;&amp;#34;,&amp;#34;url&amp;#34;:&amp;#34;sm…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @mobilenext/mobile-mcp&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `mobile_open_url` tool in mobile-mcp passes user-supplied URLs directly to Android&amp;#39;s intent system without any scheme validation, allowing execution of arbitrary Android intents, including USSD codes, phone calls, SMS messages, and content provider access.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerable code passes URLs directly to `adb shell am start -a android.intent.action.VIEW -d &amp;lt;url&amp;gt;` without checking the URL scheme. This can enable malicious schemes such as `tel:`, `sms:`, `mailto:`, `content://`, and `market://` to be executed.&lt;/p&gt;
&lt;p&gt;Since MCP servers are designed to be operated by AI agents, which are vulnerable to prompt injection attacks, a malicious document or website could inject instructions that cause the AI to execute dangerous intents on a connected mobile device.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker via prompt injection can:
- Execute USSD codes (e.g., `tel:*#06#` to display IMEI - confirmed on Pixel 7a, behavior varies by device; or device-specific factory reset codes)
- Initiate phone calls to premium rate numbers
- Draft SMS messages with attacker-controlled content
- Access content providers (contacts, SMS, call logs)
- Open app installation prompts&lt;/p&gt;
&lt;p&gt;### Proof of Concept
```json
{&amp;#34;jsonrpc&amp;#34;:&amp;#34;2.0&amp;#34;,&amp;#34;id&amp;#34;:1,&amp;#34;method&amp;#34;:&amp;#34;tools/call&amp;#34;,&amp;#34;params&amp;#34;:{&amp;#34;name&amp;#34;:&amp;#34;mobile_open_url&amp;#34;,&amp;#34;arguments&amp;#34;:{&amp;#34;device&amp;#34;:&amp;#34;&amp;lt;id&amp;gt;&amp;#34;,&amp;#34;url&amp;#34;:&amp;#34;tel:*#06#&amp;#34;}}}
```&lt;/p&gt;
&lt;p&gt;Result: IMEI displayed on device.
```json
{&amp;#34;jsonrpc&amp;#34;:&amp;#34;2.0&amp;#34;,&amp;#34;id&amp;#34;:1,&amp;#34;method&amp;#34;:&amp;#34;tools/call&amp;#34;,&amp;#34;params&amp;#34;:{&amp;#34;name&amp;#34;:&amp;#34;mobile_open_url&amp;#34;,&amp;#34;arguments&amp;#34;:{&amp;#34;device&amp;#34;:&amp;#34;&amp;lt;id&amp;gt;&amp;#34;,&amp;#34;url&amp;#34;:&amp;#34;sm…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5qhv-x9j4-c3vm</guid>
    </item>
  </channel>
</rss>
