<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Webassembly on CuraSec</title><link>https://curasec.metacog.co.kr/tags/webassembly/</link><description>Recent content in Webassembly on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 26 Oct 2026 18:39:19 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/webassembly/index.xml" rel="self" type="application/rss+xml"/><item><title>WADE: LSTM anomaly detection for WebAssembly runtime behavior</title><link>https://curasec.metacog.co.kr/insights/2026-10-26-wade-an-lstm-based-anomaly-detection-engine-for-webassembly/</link><pubDate>Mon, 26 Oct 2026 18:39:19 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-26-wade-an-lstm-based-anomaly-detection-engine-for-webassembly/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Novel behavioral detection approach for Wasm applications worth tracking if you ship WebAssembly workloads; the technique of training LSTM models on benign execution traces addresses Wasm&amp;rsquo;s lack of ASLR/stack canaries, but there&amp;rsquo;s no tooling ready to adopt yet.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> The function-trace anomaly detection methodology is conceptually applicable to future Wasm-specific detection coverage, but the research produces no IOCs, no ATT&amp;amp;CK mappings, and no detection rules to act on today.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Critical Wasmtime Sandbox-Escape Flaws Fixed; No Exploitation Reported</title><link>https://curasec.metacog.co.kr/insights/2026-10-26-two-critical-wasmtime-flaws-could-let-malicious-webassembly/</link><pubDate>Mon, 26 Oct 2026 17:20:31 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-26-two-critical-wasmtime-flaws-could-let-malicious-webassembly/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Sandbox-escape flaws in Wasmtime are critical if you embed or run it in server-side or edge workloads; no KEV or PoC yet, so urgency is moderate. Audit your dependency tree for Wasmtime and upgrade to the patched release, prioritizing ARM64 deployments.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>