<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Sandbox Escape - Tag - quactv</title><link>https://tranquac.github.io/tags/sandbox-escape/</link><description>Sandbox Escape - Tag - quactv</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>tranquac0312@gmail.com (quactv)</managingEditor><webMaster>tranquac0312@gmail.com (quactv)</webMaster><lastBuildDate>Mon, 16 Nov 2026 08:17:00 +0700</lastBuildDate><atom:link href="https://tranquac.github.io/tags/sandbox-escape/" rel="self" type="application/rss+xml"/><item><title>CVE-2026-124855 How I Escaped Firefox's Sandbox</title><link>https://tranquac.github.io/posts/firefox-sandbox-escape-cve-2026-124855/</link><pubDate>Mon, 16 Nov 2026 08:17:00 +0700</pubDate><author>quactv</author><guid>https://tranquac.github.io/posts/firefox-sandbox-escape-cve-2026-124855/</guid><description>CVE-2026-124855 / Firefox / High / November 2026
A Blob URL comparison in Firefox let a compromised content renderer cross into a privileged about:newtab context. I chained it to native code execution, reported it to Mozilla, and eventually got a CVE with my name on it.
The whole thing came down to one equality check that matched two URLs by their text and ignored the authority behind them.
How I found it I was reading through Firefox&amp;rsquo;s IPC and navigation code, mostly looking at how Blob URLs get passed between the content and parent processes.</description></item></channel></rss>