<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>sandbox-escape on VIE</title>
    <link>https://jamvie.net/tags/sandbox-escape/</link>
    <description>Recent content in sandbox-escape on VIE</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>CC Attribution-NonCommercial 4.0 International License</copyright>
    <lastBuildDate>Fri, 24 Jul 2026 11:17:42 -0600</lastBuildDate><atom:link href="https://jamvie.net/tags/sandbox-escape/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>JavaScript Sandboxes: Antipattern Review</title>
      <link>https://jamvie.net/posts/2026/07/javascript-sandboxes-antipattern-review/</link>
      <pubDate>Fri, 24 Jul 2026 11:17:42 -0600</pubDate>
      
      <guid>https://jamvie.net/posts/2026/07/javascript-sandboxes-antipattern-review/</guid>
      <description>Because the internet runs on JavaScript, and JavaScript is famously known as a language held together with paper clips and rubber bands, the topic of proper sandboxing and safe JS execution became a pretty popular discussion in the security community.
I wanted to explore some small and common gotchas that I&amp;rsquo;ve seen in recent times regarding JS sandboxes, including and based off of a real-world example I saw at work.</description>
    </item>
    
  </channel>
</rss>
