git404hub

what is cve-2026-50416-writeup-and-poc fr?

karollooool/cve-2026-50416-writeup-and-poc — explained in plain English

Analysis updated 2026-05-18

30CAudience · researcherComplexity · 5/5Setup · moderate

tl;dr

A writeup and proof of concept for a Windows 11 KASLR bypass that leaks a kernel memory pointer even from heavily sandboxed processes.

vibe map

mindmap
  root((CVE-2026-50416))
    What it does
      Documents a KASLR bypass
      Leaks kernel desktop heap pointer
      Resolves window kernel addresses
    Tech stack
      C
      Windows APIs
      Win32k internals
    Use cases
      Study Windows kernel information disclosure
      Test sandbox containment assumptions
      Reproduce the leak with the included PoC
    Audience
      Security researchers
      Windows internals engineers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Reproduce a KASLR bypass on affected Windows 11 builds using the included proof of concept.

VIBE 2

Study how sandboxed processes like browser renderers can still leak kernel addresses.

VIBE 3

Learn how the desktop heap and gSharedInfo structure can be abused to resolve window object addresses.

what's the stack?

CWindows APIsWin32k

how it stacks up fr

karollooool/cve-2026-50416-writeup-and-pocar0x4/tunnel-vision-toolkitcemsina/fasttextembed
Stars303030
LanguageCCC
Setup difficultymoderatehardeasy
Complexity5/55/52/5
Audienceresearcherresearcherdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires a specific vulnerable Windows 11 Insider build to reproduce the leak.

in plain english

This repository documents a security vulnerability found in Windows 11, tracked as CVE-2026-50416, along with proof of concept code that demonstrates it. The bug is a KASLR bypass, which means it leaks a kernel memory address that Windows normally tries to hide from regular programs. It is an information disclosure issue, not a way to run malicious code by itself, but it removes a protection that other attacks depend on. The core problem is that every Windows process which has a desktop gets a small piece of kernel memory mapped into it, called the desktop heap, so that window and menu information can be read quickly without extra system calls. At a specific offset inside this shared memory, a raw kernel pointer is exposed by mistake, one that Windows normally scrubs out before sharing it with user programs. Anyone who can read this pointer can calculate the memory address of any window or menu on the desktop, because a related structure called gSharedInfo tells you how to convert that pointer into exact addresses for specific objects. The repository includes working code that walks through this process step by step: finding the desktop heap from a thread environment block, reading the leaked pointer, and resolving it into concrete kernel addresses for several kinds of windows like buttons, edit boxes, and list boxes. What makes this notable is that the leak works even inside heavily restricted sandboxes, including the kind of low privilege, capability free sandbox that a browser uses to isolate its rendering process. The proof of concept shows that even a sandboxed process with no special permissions and no window created yet can still read this kernel address the moment it starts. Since sandboxes rely on hiding kernel memory locations as part of containing an attacker after a separate bug gives them code execution, this leak weakens that containment. This project is aimed at security researchers and people studying Windows internals or sandbox security, rather than general developers. It is a focused writeup and demonstration of one specific, now documented vulnerability rather than a general purpose tool.

prompts (copy fr)

prompt 1
Explain how the desktop heap kernel pointer leak in CVE-2026-50416 works.
prompt 2
Walk me through how gSharedInfo is used to resolve a window's kernel address.
prompt 3
Help me understand why this leak still works inside a Low integrity AppContainer sandbox.
prompt 4
Summarize the sanity checks used in this writeup to confirm the leaked value is a real kernel address.

Frequently asked questions

what is cve-2026-50416-writeup-and-poc fr?

A writeup and proof of concept for a Windows 11 KASLR bypass that leaks a kernel memory pointer even from heavily sandboxed processes.

What language is cve-2026-50416-writeup-and-poc written in?

Mainly C. The stack also includes C, Windows APIs, Win32k.

How hard is cve-2026-50416-writeup-and-poc to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is cve-2026-50416-writeup-and-poc for?

Mainly researcher.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.