Escaping AWS Firecracker from ... Note

Escaping AWS Firecracker from guest userspace: VMM memory corruption (CVE-2026-122192)

Coinspect researchers have discovered a critical vulnerability in Firecracker microVMs. This flaw allows a guest VM to access the memory of the Firecracker process itself. The vulnerability arises during snapshot restoration when using the File memory backend. A failed memory remapping can cause KVM to retain a stale host virtual address range. Firecracker might then reallocate this memory for its own use, while KVM still believes it belongs to the guest. This misattribution enables a malicious guest to read or overwrite the Firecracker VMM process memory. Exploiting this crosses the VM isolation boundary, leading to potential controlled code execution on the host. The research details an exploit chain from guest userspace to the host. Affected Firecracker versions range from 0.23.0 to 1.16.1. The vulnerable configuration requires restoring snapshots with the File memory backend and either a balloon or virtio-mem device. The issue has been patched in Firecracker versions 1.16.2 and 1.17.0+. AWS has issued a security advisory regarding this vulnerability. Coinspect's write-up thoroughly explains the vulnerability, underlying memory management, and the exploitation process.