Escaping Firecracker from Guest Userspace
Comments on “Escaping Firecracker from Guest Userspace”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Coinspect Security disclosed a Firecracker microVM escape, CVE-2026-122192, reachable from root in guest userspace. In snapshot-restored VMs using the File memory backend plus a balloon device, a failed memory-discard remap left a stale KVM slot, giving the guest access to live VMM memory. Versions 0.23.0 through 1.16.1 are affected; 1.16.2 and 1.17.0 fix it. A second seccomp bypass via io_uring is under review; AWS reports Lambda is unaffected. Coinspect tested Firecracker itself, not downstream sandbox services.
Why it ranked
No. 6 of 109 with a score of 0.75. The panel rated it highest on technical depth (0.95) and new information (0.90), lowest on audience breadth (0.66). Placed No. 6, No. 4 by score alone: the fourth Security story of the day (−0.020). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Detailed, well-evidenced sandbox escape research in Firecracker, widely used for cloud and AI agent isolation; major security significance with reproducible technical detail and fix guidance.}
- AI judgeJudge 3gpt-5.6-luna
- Detailed, technically reproducible disclosure of a Firecracker guest-to-VMM escape and seccomp bypass, with affected versions, exploit mechanics, demonstrations, and fixes. It is highly actionable for sandbox, cloud, infrastructure, and agent-security builders.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.75total under rubric v2.3
- Significance0.75
- Reader interest0.87
- Audience breadth0.66
- Practical relevance0.79
- Substantiated0.89
- Technical depth0.95
- New information0.90
- Counts against: Promotional0.17
- Counts against: Overclaim0.20
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.67 | 0.72 | 0.86 | 0.75 | 0.19 | +0.24 | +0.180 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.77 | 0.90 | 0.94 | 0.87 | 0.17 | +0.26 | +0.226 |
| Audience breadthHow many people who build technology does it concern? | 0.54 | 0.67 | 0.76 | 0.66 | 0.22 | +0.13 | +0.085 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.69 | 0.80 | 0.88 | 0.79 | 0.19 | +0.22 | +0.174 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.90 | 0.85 | 0.91 | 0.89 | 0.06 | +0.05 | +0.044 |
| Technical depthHow technically substantive is it? | 0.98 | 0.90 | 0.96 | 0.95 | 0.08 | +0.05 | +0.047 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.88 | 0.85 | 0.98 | 0.90 | 0.13 | +0.05 | +0.045 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.06 | 0.20 | 0.24 | 0.17 | 0.18 | −0.19 | −0.032 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.18 | 0.30 | 0.12 | 0.20 | 0.18 | −0.11 | −0.022 |
| Sum of contributions | +0.749 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.749 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-06/6/"><img src="https://rubric.hrih.si/badge/2026-11-06/6.svg" alt="Ranked #6 on Rubric, 6 Nov 2026" width="231" height="28"></a>Claim check
Claim check: 5 matches source · 2 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceVersion
The guest-to-Firecracker escape (CVE-2026-122192) is fixed in Firecracker v1.16.2 and v1.17.0.
The cited source says the same thing.
The article says “The guest-to-Firecracker issue is fixed in Firecracker v1.16.2 and v1.17.0”
The source says “This issue is fixed in Firecracker v1.16.2 and v1.17.0”
Source cited by the article: aws.amazon.com/security/security-bulletins/2026-169-aws
Matches sourceVersion
Firecracker versions v0.23.0 through v1.16.1 are affected by the vulnerability.
The cited source says the same thing.
The article says “Firecracker v0.23.0 through v1.16.1 are affected”
The source says “Impacted versions: Firecracker v0.23.0 through v1.16.1, inclusive”
Source cited by the article: github.com/firecracker-microvm/firecracker/security/advisories/GHSA-48ww-rqpp-2mgm
Matches sourceNumber
AWS reported in 2026 that Firecracker supports more than 15 trillion Lambda invocations per month.
The cited source says the same thing.
The article says “AWS reported in 2026 that Firecracker supports more than 15 trillion Lambda invocations per month”
The source says “Firecracker , the same lightweight virtualization technology that has powered over 15 trillions of monthly Lambda function invocations”
Source cited by the article: aws.amazon.com/blogs/aws/run-isolated-sandboxes-with-full-lifecycle-control-aws-lambda-introduces-microvms
Couldn’t checkNumber
Firecracker's GitHub security-advisory page listed two published advisories as of October 21, 2026.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “its GitHub security-advisory page listed two published advisories as of October 21, 2026”
The source says No passage could be compared.
Source cited by the article: github.com/firecracker-microvm/firecracker/security/advisories
Matches sourceQuote
AWS states that its services, including AWS Lambda, are not affected by this issue and customers need take no action.
The cited source says the same thing.
The article says “AWS states in its security bulletin that its services, including AWS Lambda, are not affected by this issue and that customers of those services need take no action”
The source says “AWS services including AWS Lambda are not affected by this issue. No customer action is required”
Source cited by the article: aws.amazon.com/security/security-bulletins/2026-169-aws
Matches sourceQuote
Vercel identifies its Firecracker microVM as the Vercel Sandbox's compute security boundary.
The cited source says the same thing.
The article says “Vercel identifies its Firecracker microVM as the sandbox’s compute security boundary”
The source says “The microVM, not the container, is the security boundary, so operator-supplied code runs two layers removed from the host”
Source cited by the article: vercel.com/blog/one-million-dollar-hacker-challenge-for-vercel-sandbox
No source givenQuote
AWS classifies FC-03 as a defense-in-depth improvement requiring prior VMM compromise and does not plan to assign it a CVE or separate advisory.
The article gives no link or citation for it.
The article says “AWS classifies FC-03 as a defense-in-depth improvement because it requires prior VMM compromise and does not plan to assign it a CVE or issue a separate advisory”
The source says No source to compare with.
No source givenNumber
Coinspect estimates a researcher working without Codex would have needed roughly 20 times as long to reach comparable confidence.
The article gives no link or citation for it.
The article says “we estimate that a researcher working without Codex would have needed roughly 20 times as long to reach comparable confidence”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 6 pts, not on front page
Recorded for context only, checked 6 Nov 2026, 05:47 UTC. It played no part in the ranking.