V4bel (@v4bel) profile picture

Independent Vuln. Researcher / Pwn2Own Berlin 2025, 2026 / Google kernelCTF 0-day / Google kvmCTF 0-day / Pwnie Awards 2025, 2026

Joined November 2019
Photo by V4bel (@v4bel)Photo by V4bel (@v4bel)Photo by V4bel (@v4bel)Photo by V4bel (@v4bel)Photo by V4bel (@v4bel)Photo by V4bel (@v4bel)Photo by V4bel (@v4bel)Photo by V4bel (@v4bel)Photo by V4bel (@v4bel)Photo by V4bel (@v4bel)
Pinned Tweet
NoisyTCP: Linux Kernel TCP Pre-auth Remote Corruption CVE-2026-99288. "11 years" latent. Patch it. The era of KVM escapes is fading, and the era of TCP remote exploits has begun. github.com/V4bel/NoisyTCP
19
115
17
525
47,115
23eaaff88a99869eef3d243b1899e99ffd5820765683561b3750112ee5a67576
1
2
30
4,539
Galaxy S26 Ultra: untrusted_app → root. Introducing "Infinity Core": 6 vulns in the Linux kernel's core subsystems. Their impact spans Linux server LPE, container escape, and Android LPE. Details: github.com/V4bel/InfinityCor…
20
107
7
857
56,409
Plain old LPEs are getting a little boring, so I audited the kernel's relatively underexplored core subsystems and found 6 bugs. These were vulns I'd originally found with kernelCTF in mind. And these days, I hardly do any LPE research at all 🙄
2
39
5,680
Nice. This year is the year of the VM escape. But I read the kvm ML and tree daily, and nothing in the recent public kvm patches looks like a microvm escape. Probably not "kvm" but another virt stack. Maybe I missed it, or a stealth merge is coming. Curious either way.
We’ve confirmed a KVM 0day through our Vercel Sandbox bounty program. Affecting the industry’s gold standard solution for Linux virtualization. 2026 is wild! Thankful to Paulos and other researchers helping us make the most secure sandbox for agents. Full writeup coming.
9
1
100
7,971
Another month, another KVM escape. Patch if you're affected. openwall.com/lists/oss-secur…
3
21
2
116
10,334
Won Best RCE and Best PE at the Pwnie Awards 2026 🏆🏆 Three of my projects were nominated this year, and ITScape and Dirty Frag took home the awards. That makes three Pwnies in total, following last year’s Best PE. Pwnie is probably the award that motivates me the most. Next year’s goal: find a vuln that destroys the world ;) Thank you, @PwnieAwards!
7
19
1
189
16,582
Thanks to @_qwerty_po for accepting the awards on my behalf while I was sick.
11
2,090
💥 Introducing "Zapscape" (CVE-2026-64561) A Guest-to-Host Escape in KVM/x86 exploiting a UAF in the shadow MMU's recursive "ZAP" path. Can escape to the host on x86 public clouds that expose nested virtualization. A separate vulnerability from Januscape. If you match the vulnerable conditions, apply the patch immediately. Details: zapscape.io
5
75
4
358
31,880
This completes the KVM Escape Trilogy. Hopefully there will be no sequel :/
2
21
1,951
Interesting.
Nous avons terminé la compagne de patching du jbug critique CVE-2026-53359 dans KVM. Vu le niveau critique du bug, nous n'avons pas communiqué avant de démarrer le patching, il fallait aller vite. Maintenant que l'infra est en sécurité, voici le REX. blog.ovhcloud.com/campagne-d…
12
6,113
"Januscape" only triggers on Intel and AMD hosts, but if you still haven't patched "ITScape", your arm64-based hosts are at risk too, so apply the patch promptly. teapawt.org/v4bel/status/206477614…
🚨 Introducing "ITScape" (CVE-2026-46316) A Guest-to-Host Escape in KVM/arm64. Guest-side actions alone exploit a use-after-free to run root-privileged code in the host kernel. Unlike the commonly published QEMU escapes, the bug lives in in-kernel KVM, not QEMU. On a successful exploit, commands run with host kernel privilege rather than the privilege of a user process, threatening the guest-host isolation of multi-tenant arm64 public clouds. To the best of public knowledge, the first Guest-to-Host Escape Exploit targeting in-kernel KVM/arm64. Details: itscape.io
1
10
6,181
Anyway, this wraps up my cute tux series. The face is especially funny, isn't it? lol - Dirty Frag: Universal Linux LPE - ITScape: The first Guest-to-Host Escape in KVM/arm64 - Januscape: The first Guest-to-Host Escape in KVM/x86 && Google kvmCTF 0-day exploit
🤖 Made with AI
2
1
1
23
3,200
💥 Introducing "Januscape" (CVE-2026-53359) A Guest-to-Host Escape in KVM/x86 exploiting a UAF in the shadow MMU. Triggerable on both Intel and AMD hosts. Threatens x86 public clouds (GCP, AWS) that expose nested virtualization. "16 years" latent. Successfully used as a 0-day exploit in "Google kvmCTF". To the best of public knowledge, the first KVM exploit research triggerable on both Intel and AMD. Details: januscape.io
7
105
8
448
62,588
🚨 Introducing "ITScape" (CVE-2026-46316) A Guest-to-Host Escape in KVM/arm64. Guest-side actions alone exploit a use-after-free to run root-privileged code in the host kernel. Unlike the commonly published QEMU escapes, the bug lives in in-kernel KVM, not QEMU. On a successful exploit, commands run with host kernel privilege rather than the privilege of a user process, threatening the guest-host isolation of multi-tenant arm64 public clouds. To the best of public knowledge, the first Guest-to-Host Escape Exploit targeting in-kernel KVM/arm64. Details: itscape.io
4
92
3
308
37,229
The patch addressing several Dirty Frag variants has been merged into netdev tree. Details: seclists.org/oss-sec/2026/q2…
18
3,011