<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mobile on CuraSec</title><link>https://curasec.metacog.co.kr/tags/mobile/</link><description>Recent content in Mobile on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 29 Oct 2026 17:24:45 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/mobile/index.xml" rel="self" type="application/rss+xml"/><item><title>Telegram Android RCE Triggered by Answering Voice Calls, Patched in v12.10.4</title><link>https://curasec.metacog.co.kr/insights/2026-10-29-telegram-android-flaw-lets-attackers-run-code-when-users-ans/</link><pubDate>Thu, 29 Oct 2026 17:24:45 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-29-telegram-android-flaw-lets-attackers-run-code-when-users-ans/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> One-interaction RCE requiring only an attacker Telegram account is a high-severity mobile risk; verify corporate or BYOD devices are running Telegram ≥ 12.10.4 via MDM policy or device-compliance checks. No exploitation signals yet, so this is a patch-window item rather than emergency.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation, IOCs, or ATT&amp;amp;CK-mappable TTPs have been published; the voice-call RCE vector is worth logging for context when triaging future mobile-related incidents, but there is nothing actionable to detect or hunt today.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>