Forshaw’s ‘Dumb’ UAC Bypass: MS Won’t Fix 16 of 27 Defences

James Forshaw, a Windows security researcher at Google Project Zero, says he has found a “really dumb” way around User Account Control, the Windows prompt that asks before an app gets administrator rights. In a post on 17 November he wrote: “no doubt the thing I’m abusing was vibe coded to within an inch of it’s life”.

Our number: Microsoft’s own servicing criteria list 27 Windows security features, and for 16 of them, UAC included, Microsoft answers No to “Intent is to service?”, by our count of Microsoft’s table.

Business Pill · Least Privilege

An evergreen Business Engineer explainer on least privilege and access control. It teaches the general idea only and does not discuss this bypass.

The key insight: Forshaw says a UAC bypass he found is ‘really dumb’ and that the code was ‘vibe coded’, but UAC is one of 16 of the 27 features in Microsoft’s servicing criteria that Microsoft does not intend to service, by our count.

What Forshaw Posted

Forshaw’s full post reads: “I know UAC bypasses are not a thing MS need to think about but one I’ve just found is really dumb, no doubt the thing I’m abusing was vibe coded to within an inch of it’s life”. He did not name the Windows component or publish technical details in the posts we read.

In a reply 43 minutes later, Forshaw wrote that Administrator Protection “is back in latest versions of Windows 11, you can turn it on through local security policy”. Microsoft describes the feature as offering “robust security and user privilege management”. Forshaw added: “There’s been some rumours they’ll force it on at some point, at least for enterprise”. International Cyber Digest relayed his first post on X on 18 November.

Microsoft's Windows servicing criteria list 27 security features; for 16, including User Account Control, the
Microsoft’s Windows servicing criteria list 27 security features; for 16, including User Account Control, the answer under ‘Intent is to service?’ is No, by our count. Source: Microsoft (MSRC).

Why Microsoft Does Not Patch It

Microsoft’s security servicing criteria for Windows list UAC under “User safety”, with the goal to “Prevent unwanted system-wide changes (files, registry, etc) without administrator consent”, and answer No under both “Intent is to service?” and “Bounty?”. The other 15 features with a No include Data Execution Prevention, ASLR, Control Flow Guard, AppLocker and Mark of the Web; 11 of the 27 have a Yes, by our count.

Microsoft introduced Administrator protection on 19 November 2024, writing: “Our goal is to enable Administrator protection by default in Windows very soon”. An editor’s note on the same page now says it “is now available and is off by default”. That is 729 days after the November 2024 post, by our arithmetic.

Where This Fits

Our recent cyber coverage has been about AI finding flaws: the Java4Shell bug, reported patching of AI-found flaws behind US outages and Reflection’s gated Laser hacking agent. Forshaw’s post makes a different claim: that the weak code was itself vibe coded.

The Structural Read

As we read Microsoft’s table, a UAC bypass is a design question for Microsoft rather than a patch: the fix it has offered is Administrator Protection, which its own page says is off by default.

As we read Forshaw’s post, the claim about AI-written code is an expert’s guess, not a finding; it matters because he is one of the researchers best placed to judge Windows code.

James Forshaw, Google Project Zero, on infosec.exchange

“no doubt the thing I’m abusing was vibe coded to within an inch of it’s life”

Three Implications

FOR WINDOWS ADMINISTRATORS Forshaw says Administrator Protection can be turned on through local security policy in the latest Windows 11 builds.

FOR MICROSOFT Microsoft wrote in November 2024 that its goal was to enable Administrator protection by default very soon; its page now says it is off by default.

FOR AI CODING TOOLS Forshaw’s post puts a named researcher’s suspicion of vibe-coded code inside Windows on the record, without proof.

The Business Engineer Lens

This story maps onto the Business Engineer framework The Agentic Harness War.

The analysis puts it this way: “Proliferation wins where work is embedded in legacy tools and human review is non-negotiable — regulated industries, relationship-driven roles, judgment-heavy domains.”

As we read Forshaw’s post, operating-system code is a domain where human review should be non-negotiable; the analysis predates his post and does not discuss it.

What Is Not Established

Forshaw’s “no doubt” is his own view, not evidence that AI wrote the code; he gave no proof and did not name the component. We have not seen the bypass, a write-up or a Project Zero report, and we did not contact Microsoft or Forshaw. Forshaw calls talk of Microsoft forcing Administrator Protection on a rumour.

This Week In The AI Supercycle

AI Lost Its Central Banker, the Lab Oligopoly, and the Future of Open Source

This week’s issue: the Nvidia leadership change, read as the AI build-out losing its central banker: who now finances the GPU landlords, backstops the data centres and sponsors open models, and why two labs are becoming the bank.

Read the full issue →

Business Engineer Framework

The Agentic Harness War

A Business Engineer analysis of how agent harnesses compete, and where human review stays in the loop.

Read the Map of AI →

The Bottom Line

A Project Zero researcher says a UAC bypass he found is “really dumb” and blames vibe coding, but Microsoft does not service UAC bypasses: UAC is one of 16 of the 27 features in its servicing criteria marked No, by our count.

97,000+ executives read Business Engineer for the AI strategy frameworks cited by ChatGPT, Claude, and Perplexity.

A note on sourcing. Forshaw’s words are from his own two posts on infosec.exchange, read in full. The servicing table is Microsoft’s, read on 18 November 2026; the 16, 27 and 11 counts are ours. The 729 days and the 43 minutes are our arithmetic from the dates and timestamps. We did not contact Microsoft or Forshaw.

Sources: James Forshaw, infosec.exchange, 17 Nov 2026 · James Forshaw reply, 17 Nov 2026 · Microsoft Security Servicing Criteria for Windows · Microsoft Windows IT Pro Blog, 19 Nov 2024 · International Cyber Digest on X, 18 Nov 2026

Scroll to Top
FourWeekMBA