gitwtfhub

wtf is cve-2026-49176_lpe_poc?

davidcarliez/cve-2026-49176_lpe_poc — explained in plain English

Analysis updated 2026-05-18

10CAudience · ops devopsComplexity · 4/5Setup · moderate

TL;DR

A proof of concept demonstrating a since-patched Windows bug that let a regular user gain full system-level access through the WalletService component.

Mindmap

mindmap
  root((CVE-2026-49176 PoC))
    What it does
      Demonstrates a WalletService bug
      Escalates user to SYSTEM
      Already patched by Microsoft
    Tech stack
      C
      PowerShell
      Windows 11
    Use cases
      Verify a system is patched
      Study privilege escalation
      Security research
    Audience
      Security researchers
      IT professionals
    Details
      Root cause writeup
      Build scripts included

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

Why would anyone build with this?

REASON 1

Verify whether a Windows 11 machine still has the WalletService vulnerability unpatched

REASON 2

Study how a folder redirection trick can trick a privileged service into loading attacker code

REASON 3

Reproduce the exploit in a test environment for security research

REASON 4

Rebuild the included proof of concept binaries using Visual Studio build tools

What's in the stack?

CPowerShellWindows 11

How it stacks up

davidcarliez/cve-2026-49176_lpe_pocalexzorzi/inferno-androiddanterolle/tund
Stars10109
LanguageCCC
Setup difficultymoderatehardmoderate
Complexity4/55/53/5
Audienceops devopsdeveloperdeveloper

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

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Only works on unpatched Windows 11 25H2 build 26200.8737, requires Visual Studio build tools to rebuild binaries.

Wtf does this do

This repository is a proof of concept for a specific Windows security bug, tracked as CVE-2026-49176, which Microsoft already fixed in a July 2026 update. It demonstrates how a regular, non-administrator user on an affected Windows 11 machine could gain full system-level control, the highest level of access on the computer, by exploiting a flaw in a background component called WalletService. The technique works because WalletService looks up the location of the user's Documents folder while briefly acting as that user, but then switches to running with full system permissions before it opens a specific database file inside that folder. A regular user can point their own Documents folder somewhere they control, place a specially prepared database file there, and have that file contain a reference to a piece of code the user supplies. When WalletService opens the file while running with full permissions, it ends up loading and running that user-supplied code with the highest level of access instead of the user's own limited access. To run the demonstration on a still-vulnerable, unpatched Windows 11 system, a user opens a regular, non-administrator PowerShell window and runs a provided script, or simply double-clicks a batch file. If the machine is vulnerable, a new command prompt opens showing full system-level access. The repository also includes a build script for rebuilding the included program files using Microsoft's Visual Studio build tools, and a separate written technical explanation is linked for readers who want the full details of how the bug was found and works. This project is intended for security researchers and IT professionals who want to understand or verify the vulnerability, for example to confirm a system has been patched. It only affects systems that have not yet installed the July 2026 security update, and the README does not mention a license.

Yoink these prompts

Prompt 1
Explain how the WalletService privilege escalation in CVE-2026-49176 actually works
Prompt 2
Walk me through safely testing this proof of concept on an isolated Windows 11 VM
Prompt 3
Help me confirm whether my Windows 11 build already has this July 2026 patch
Prompt 4
Summarize the root cause of this vulnerability for a non-technical security report

Frequently asked questions

wtf is cve-2026-49176_lpe_poc?

A proof of concept demonstrating a since-patched Windows bug that let a regular user gain full system-level access through the WalletService component.

What language is cve-2026-49176_lpe_poc written in?

Mainly C. The stack also includes C, PowerShell, Windows 11.

How hard is cve-2026-49176_lpe_poc to set up?

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

Who is cve-2026-49176_lpe_poc for?

Mainly ops devops.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.