AmazonAnalysisAWS fixes guest-to-host process memory access defect in Firecracker
What happened.Amazon Web Services issued security bulletin 2026-169-AWS resolving a memory isolation defect in the open-source Firecracker microVM monitor.
Why it matters.MicroVM monitors isolate untrusted serverless functions from shared host kernels. When memory discard errors fail to reclaim guest mappings correctly, root access in a sandboxed guest translates into memory corruption on the host hypervisor. Engineers maintaining private serverless platforms must upgrade to Firecracker v1.16.2. Platform operators should migrate snapshot pipelines to userfaultfd backends to ensure memory safety.
The technical specifications:
- Vulnerability mechanics: Tracked as CVE-2026-122192, the flaw enables root users inside guest VMs to read or alter host Firecracker VMM memory following failed discard operations.
- Trigger conditions: The defect impacts microVMs restored from snapshots using File backends configured with balloon or virtio-mem devices.
- Service isolation: AWS confirmed managed services including AWS Lambda are unaffected, with exposure limited to self-managed Firecracker virtualization stacks.
- Affected versions: The vulnerability impacts open-source Firecracker v0.23.0 through v1.16.1 deployed in custom serverless infrastructure.
- Remediation release: AWS published Firecracker v1.16.2 and v1.17.0, recommending operators switch snapshots to the userfaultfd backend.