← All stories
● Covered by 1 source · 1 reportMedium impact1 negative

Firecracker MicroVM Escape Achieved, Allowing Root Code Execution on Host

🔄 Updated 23h ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Escaped Firecracker microVM to gain root access on host.
  • Exploit modifies saved registers of a vCPU thread.
  • Redirects execution upon return from KVM_RUN system call.
  • Uses a host memory primitive identified in PwnEscape Part 1.

Firecracker MicroVM Escape Details

Researchers have demonstrated a method to escape a Firecracker microVM, resulting in root code execution on the host machine. The exploit involves manipulating the Firecracker process that manages the microVMs, specifically targeting the virtual CPU (vCPU) threads.

The attack modifies the saved registers of a vCPU thread while it is within the KVM_RUN system call. By changing the instruction pointer and stack pointer in the pt_regs structure, the researchers can control where Firecracker resumes execution when the thread returns to userspace.

Exploitation Mechanism

The core of the exploit relies on a host memory primitive previously identified in "PwnEscape Part 1." This primitive provides access to selected host physical memory from within the guest. Using this access, the researchers located the Firecracker process in memory and identified the register frame belonging to the active vCPU thread.

A recognizable byte pattern, or nonce, placed in a guest page was used to find the guest page on the host, bridging the guest and host physical address spaces via Extended Page Tables (EPT).

Impact and Context

This vulnerability, identified as CVE-2026-99999, demonstrates that untrusted code within a Firecracker microVM can potentially compromise the host system. The exploit allowed the guest to restore temporary stack changes, with Firecracker continuing to run and the VM remaining accessible over SSH, indicating a stealthy compromise.

Firecracker is designed to isolate untrusted code within microVMs, making this escape a significant finding for environments relying on Firecracker for security boundaries.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 07

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Researchers successfully escaped a Firecracker microVM, achieving root code execution on the host system. This exploit, a continuation of previous work, leverages a host memory primitive to modify saved registers and redirect execution when a vCPU thread returns from KVM.