How a Single Pull Request Could Have Exposed a Microsoft WinGet Moderator’s GitHub Token

A flaw in Microsoft's internal review automation could have sent a moderator's broad GitHub credential to an attacker-controlled server without any action from the moderator.

Published on Nov 19, 2026
Microsoft logo on an office building

Last updated Nov. 19, 2026: This story has been updated with a response from Microsoft.

A single pull request to Microsoft’s WinGet package catalog could have handed an attacker a Microsoft moderator’s GitHub token, according to researchers who found the flaw in the moderators’ own review automation.

Microsoft has since fixed it, and told Expert Insights it had nothing further to share.

WinGet, Microsoft’s free, open-source command-line package manager, runs on more than 1.4 billion active Windows 10 and 11 devices, researchers at Cycode said. Its catalog lives in a public GitHub repository, where a small team of Microsoft moderators reviews pull requests submitted by the community.

The problem sat in a PowerShell triage tool the moderators use to process those submissions, not in the catalog. Whenever the tool made a web request, it included the moderator’s GitHub Personal Access Token (PAT), regardless of which server the request went to.

How a Routine Check Could Send the Token to an Attacker

Part of the tool’s automated checks took the installer URL listed in a submitted manifest and called it. An attacker could therefore open a pull request whose URL led to a server under their control. Once that URL failed validation, the moderator’s tool followed up on it automatically as part of its routine background loop, passing the token to the attacker’s server in the process.

The moderator didn’t need to approve or click anything, only to have the tool running as designed. The tool also left a comment on the pull request noting the response it had received, which Cycode said would tell the attacker the token had been delivered.

The token was a Classic PAT with the “workflow” scope, which Cycode called “a full identity credential”: anything the moderator could do on GitHub, the token could do too.

What the Token Unlocked, and How Microsoft Fixed It

With it, Cycode said, an attacker could have pushed malicious manifests directly and approved their own pull requests across 14,000 packages, and written to other Microsoft repositories the moderator could reach.

Because of the workflow scope, they could also have altered GitHub Actions workflows to run code on continuous integration and delivery (CI/CD) runners and take the secrets stored there.

Microsoft closed the gap in pull request #456300, which limits the token to requests bound for approved GitHub addresses. Cycode also recommended replacing Classic tokens with fine-grained ones scoped to a single repository.

The company said it came across the flaw while building its AI offensive security capabilities, and credited the Microsoft Security Response Center (MSRC) and the WinGet maintainers with responding quickly as part of a coordinated disclosure.

This field is for validation purposes and should be left unchanged.

FREE NEWSLETTER

Cyber Weekly

Get curated cybersecurity news, threats and insights delivered free every Thursday.

Written By Written By
Alessandro Mascellino
Alessandro Mascellino Cybersecurity Reporter

Alessandro Mascellino is a British-Italian freelance journalist specializing in technology and gaming. He has contributed to several publications, including Wired, The Independent, and Android Police. By day, he works as a journalist. By night, he co-manages a game studio that creates narrative games.