CopyFail: From Pod to Host
Copy Fail is a new Linux vulnerability that allows attackers to escape containers and gain root access. It exploits a kernel memory corruption flaw without injecting code, making it particularly dangerous. The vulnerability enables controlled writes to the Linux page cache, allowing for the manipulation of files and potential backdoor access to co-located pods.
- ▪Copy Fail is identified as CVE-2026-31431 and is a local-privilege escalation vulnerability.
- ▪The exploit allows attackers to rewrite cached contents of files on a Linux filesystem, including setuid binaries like 'su'.
- ▪There are two main attack scenarios: cross-container poisoning and container escape, both leveraging the shared page cache across containers.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Hacker News (Newest) |
| Canonical URL | https://xint.io/blog/copy-fail-pod-to-host |
| Publication time | Tue, 19 May 2026 17:25:33 +0000 |
| Retrieval time | 2026-05-19T17:34:57.931Z |
| Last seen | 2026-05-19T17:34:57.931Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 60um8r6p-Bn9 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Vulnerability ResearchAI for SecurityOpen Source ProjectsCopy Fail: From Pod to Host.A walkthrough of Copy Fail (CVE-2026-31431) as a container escape primitive: from a 4-byte page cache write to host root on Kubernetes.Juno ImMay 19, 2026ContentsWhy the Page Cache Crosses Container BoundariesScenario 1: Cross-Container Poisoning1-1: Compromised pod sharing a base layer1-2: Pod creation rightsScenario 2: Container EscapeDetection and MitigationCommunity PoCsTwo weeks ago, we disclosed Copy Fail, a new and exceptionally dangerous Linux local-privilege escalation vulnerability. Copy Fail exploits a kernel memory corruption flaw without injecting code into a running kernel, which makes it small and unusually portable.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (Newest).