<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Flask on CuraSec</title><link>https://curasec.metacog.co.kr/tags/flask/</link><description>Recent content in Flask on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 12 Oct 2026 20:16:55 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/flask/index.xml" rel="self" type="application/rss+xml"/><item><title>Researcher earns $90k for Flask pickle RCE on Google devsite</title><link>https://curasec.metacog.co.kr/insights/2026-10-12-i-found-a-90k-remote-code-execution-vulnerability-in-google/</link><pubDate>Mon, 12 Oct 2026 20:16:55 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-12-i-found-a-90k-remote-code-execution-vulnerability-in-google/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> A concrete real-world example of pickle deserialization RCE via Flask session cookies — audit any internal Flask apps using custom pickle-backed session stores and prefer signed, non-pickle serialization formats instead.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation or IOCs to act on; the writeup is useful background on pickle deserialization as an RCE vector for future detection engineering, but yields no immediate hunt or rule work.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>