Vercel’s KVM zero-day: viddy the missing fine print

Viddy the comforting little box, droogies. It was doing excellent work in the architecture diagram.

On October 3, Vercel CEO Guillermo Rauch said the company had confirmed a KVM zero-day through its Sandbox bounty program. Researcher Paulos Yibelo separately claimed an escape from a guest virtual machine to root access on its host. Rauch promised a full write-up.^[2][3]

What’s on the receipt

• Yibelo posted a bounty notice showing a $50,000 award. The report’s root cause is blacked out.
• Vercel’s published challenge capped individual awards at $50,000. The much louder $1 million headline described the total reward pool.
• Vercel says its Sandbox runs each workload in a Firecracker microVM on a bare-metal EC2 host. That microVM is the security boundary.^[3][4]

What’s still behind the curtain

The announcements do not give a CVE, affected versions, exploit prerequisites or a patch. They do not establish customer data theft or widespread exploitation. A confirmed KVM finding is no licence to declare every cloud host cracked open.^[1][2][3]

Paying someone to test the lock is sensible. Now comes the less glamorous bit: tell operators which lock, which fault and which fix. Keep your gulliver on those details while the victory graphics render.