# Two Firecracker microVM escapes in one week: what CVE-2026-122192 and PwnEscape Part 2 mean for AI sandboxes, and what to patch

> Coinspect disclosed a Firecracker bug that lets a root user in a guest take over the VMM process, and PWN AI published a full exploit that chains a Linux host-kernel flaw into root on a Firecracker host. Both are fixed upstream, but anyone running their own Firecracker or KVM hosts for agent sandboxes, CI or multi-tenant code needs to update Firecracker and the host kernel and turn on the jailer.

Published Nov 7, 2026 by TechMeasured Staff · Security · Canonical: https://techmeasured.com/security/firecracker-two-microvm-escapes-cve-2026-122192-pwnescape-what-to-patch

**Firecracker**, the lightweight virtual-machine monitor AWS built for Lambda and that many AI-agent and code-sandbox platforms now use to isolate untrusted code, has had two separate guest-to-host escapes made public this week. On **November 4**, security firm **Coinspect** disclosed **CVE-2026-122192**, a Firecracker memory bug that lets root inside a guest take over the Firecracker process. On **November 6**, **PWN AI** researcher **Paulos Yibelo** published "PwnEscape Part 2", a write-up with proof-of-concept code showing root code execution on a Firecracker host by chaining a Linux host-kernel flaw, **CVE-2026-99999**.

Why it matters: the whole point of a microVM sandbox is that code inside it — an AI agent's shell commands, a customer's CI job, a stranger's script — cannot touch the machine underneath. Both bugs are already fixed upstream, so the risk sits with teams that run **their own** Firecracker or KVM hosts and haven't updated.

## Escape 1: CVE-2026-122192, a stale memory mapping in Firecracker

According to Coinspect's **Juan Pablo Martinez Kuhn**, the bug is in how Firecracker discards guest memory for microVMs restored from snapshots. If replacing a memory mapping fails partway, Firecracker only logged the error while the guest kept access to that address range — which Firecracker could later reuse for its own data. The guest could then read and change live VMM memory and get code execution in the Firecracker process.

Coinspect says the conditions are specific:

- the microVM was **restored from a snapshot** using the File memory backend;
- it has a **balloon or virtio-mem** device the guest can use to request memory discards;
- the attacker has **root inside the guest** (no guest-kernel code was needed);
- guest memory pressure hits a configured per-microVM memory limit.

Coinspect also reported a second issue, **FC-03**: Firecracker's default seccomp filter allowed `io_uring` setup, so code already running in the VMM could open a fresh ring and perform host operations seccomp would otherwise block. In its tests that included reaching a host loopback listener — but only when the jailer ran without its own network namespace (`--netns`). AWS treats FC-03 as defence in depth, with no separate CVE; a seccomp change (PR #6287) is under review.

| Item | Detail (per Coinspect) |
|---|---|
| Affected | Firecracker v0.23.0 through v1.16.1 |
| Fixed | v1.16.2 and v1.17.0 (released Sept 10, 2026) |
| Advisory | CVE-2026-122192, GHSA-48ww-rqpp-2mgm, published Nov 4 |
| AWS services | AWS's bulletin says Lambda and other AWS services are not affected |

Coinspect notes the fix was merged on September 1 without describing its security impact — so anyone who tracks releases rather than advisories may not have prioritised it.

## Escape 2: PwnEscape Part 2, from a host-kernel bug to root

PwnEscape started as a Linux networking bug, not a Firecracker one. Per PWN AI's Part 1 and Rescana's advisory summary, a guest could send packets with crafted checksum-offload hints that made the **host** kernel rewrite an IPv4 header after it had been checked, leaking host memory and enabling memory writes. The code dates back to Linux 2.6.27 in 2008. Yibelo found it during Vercel's sandbox challenge; the fix (commit `6785011f8b16`) reached mainline on October 14. The Linux kernel CNA scores it **9.3** (Red Hat rates it 8.8).

Part 2 uses that primitive to locate the Firecracker process in host memory, find a vCPU thread's saved registers and redirect its return path so Firecracker executes attacker-chosen code as root, then puts everything back so the guest keeps running. PWN AI says it tested Firecracker **v1.16.1** on an AWS-flavoured 7.0 host kernel, **without the jailer**, and that a production setup with the jailer's privilege dropping, namespaces and seccomp "requires a separate assessment". The final stage is tied to a specific Firecracker build. An independent review on DEV Community checked the commit and Firecracker code paths but could not rerun the exploit.

Upstream fixed kernels include 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.57 and 7.2.11, according to Rescana. As of October 31 it listed RHEL, AlmaLinux and Debian as fixed and **Ubuntu** as still waiting on kernel updates. No in-the-wild exploitation has been reported.

## What to do

1. **Update Firecracker** to v1.16.2, v1.17.0 or later, and check any fork or embedded copy.
2. **Patch the host kernel** for CVE-2026-99999 and reboot (migrate guests first). Rescana notes no vendor offers a full workaround; patching guests alone is not enough.
3. **Run every microVM under the jailer**, with its own network namespace (`--netns`). Both write-ups show how much worse things get without it.
4. **On Ubuntu hosts**, check Canonical's CVE tracker; if your kernel is still unfixed, consider moving untrusted workloads to patched hosts.
5. If you rely on a **hosted** sandbox (agent runtimes, CI, code-execution APIs), ask the provider whether its hosts are patched — Coinspect explicitly did not assess third-party services.


## Sources

1. [Coinspect — Escaping Firecracker from Guest Userspace](https://www.coinspect.com/blog/firecracker-escape/)
2. [PWN AI — Firecracker VM Escape: PwnEscape Part 2](https://pwn.ai/blog/firecracker-escape)
3. [PWN AI — PwnEscape (Part 1)](https://pwn.ai/blog/pwnescape)
4. [Rescana — PwnEscape CVE-2026-99999: Linux Kernel Guest-to-Host Escape, Patch VM Hosts Now](https://www.rescana.com/post/linux-kernel-pwnescape-cve-2026-99999-guest-to-host-prepare-now)
5. [DEV Community — 9.3 to root in 5 hops: I audited the Firecracker escape](https://dev.to/frankchu/93-to-root-in-5-hops-i-audited-the-firecracker-escape-4fhn)
