Skip to content- Sources: primary, discussion
- Summary: Coinspect showed that a failed memory discard in Firecracker v0.23.0 through v1.16.1 left a KVM memory slot pointing at reused VMM memory, letting root in guest userspace read and change Firecracker's host process and gain code execution. A second issue, FC-03, let that code create a fresh io_uring ring to perform host operations the seccomp policy blocks, and a seccomp redesign for it is still under review in PR 6287 with no CVE planned. AWS published the CVE, GHSA-48ww-rqpp-2mgm and a bulletin on 2026-11-04 and says Lambda and its other services are not affected.
- Why it matters: Teams that self-host Firecracker for agent or untrusted code sandboxes should upgrade, check for file-backed snapshot plus balloon or virtio-mem setups, and consider running the jailer with --netns.
- Follow-up: Review and merge of the FC-03 seccomp redesign in Firecracker PR 6287.