<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Browser-Rce on CuraSec</title><link>https://curasec.metacog.co.kr/tags/browser-rce/</link><description>Recent content in Browser-Rce on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 29 Jul 2026 13:07:14 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/browser-rce/index.xml" rel="self" type="application/rss+xml"/><item><title>Firefox JIT Flaw CVE-2026-10702 Enables Single-Visit RCE in Tor Browser</title><link>https://curasec.metacog.co.kr/insights/2026-07-29-researchers-show-a-single-malicious-webpage-visit-can-compro/</link><pubDate>Wed, 29 Jul 2026 13:07:14 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-29-researchers-show-a-single-malicious-webpage-visit-can-compro/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> A public PoC on GitHub for a no-interaction arbitrary code execution flaw in Firefox&amp;rsquo;s renderer means drive-by exploitation is immediately practical; update Firefox to 151.0.3 across all managed endpoints and verify Tor Browser is similarly patched or blocked.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> With a public PoC now circulating, watering-hole operators may weaponize this quickly; build or tune detections for unexpected child processes spawned from the Firefox renderer process and prepare a hunt query scoped to the weeks before the 151.0.3 fix shipped.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> CVE-2026-10702 — CISA KEV: not listed, EPSS 0.01, public PoC on GitHub&lt;/li>
&lt;/ul></description></item></channel></rss>