Infographic showing an allowlist gateway securely routing a moderator tool’s GitHub requests while blocking untrusted destinations.
Cycode says one pull request could have leaked a Microsoft moderator's GitHub token from the WinGet community repository. Microsoft has since changed the moderators' triage tool so the token no longer goes to arbitrary hosts. The fix is visible in a public pull request. Cycode's severity and scale claims are not independently confirmed.

Infographic showing an allowlist gateway securely routing a moderator tool’s GitHub requests while blocking untrusted destinations. What was reported​

Cycode's research lead Moriel Harush published the findings on November 18, 2026. The flaw sat in ManualValidationPipeline.ps1, a PowerShell triage script used by moderators of microsoft/winget-pkgs. That repository is the public GitHub catalog behind the default WinGet source. As a background point, an MSEndpointMgr analysis describes it as the default WinGet source, a giant tree of YAML manifests describing where installers live and how to run them.

According to Cycode, the script's HTTP helper attached the moderator's GitHub Personal Access Token to outgoing requests. It did this without checking where the request was going. One automated code path also read a URL from a submitted package manifest and requested it.

The company says it found the issue while building AI-assisted offensive security tooling. That is the vendor's own account of how it was found.

The reported attack chain​

Cycode describes a four-step chain that needs no moderator interaction after the pull request is opened:

  1. Bait. The attacker opens a pull request with an InstallerUrl pointing at a server they control.
  2. Trigger. Cycode says Microsoft's Azure DevOps validation pipeline fetched that URL. The attacker's server returned an error, which caused a URL-Validation-Error label to be applied.
  3. Hook. A moderator's continuously running triage loop saw the label. It ran a CheckInstaller routine, which sent a HEAD request to the attacker's URL.
  4. Catch. The request went through the authenticated helper, so the bearer token reached the attacker's server logs.

Cycode adds that the tool then posted a PR comment recording the HTTP status code. That would have told the attacker the request had landed.

The only stated precondition is that at least one moderator was running the tracker in its intended always-on mode. "Zero-click" here means no moderator had to open the link or the PR.

Cycode's analogy: a courier staples your house key to every parcel with your name on it. That is fine until someone writes your name on a parcel addressed to themselves.

Why the token mattered​

Cycode says the exposed credential was a Classic PAT with the workflow scope. It argues that this is a full identity credential, not one limited to a single repository. On that basis it lists what a thief could attempt:

  • Push manifests to winget-pkgs and approve their own pull requests.
  • Write to other Microsoft repositories the moderator can reach.
  • Alter GitHub Actions workflows to run code on CI runners and reach pipeline secrets.

These are potential outcomes, not documented incidents. None of the sources I reviewed shows a token being stolen. They also show no malicious package being published, and no compromise of Microsoft's wider GitHub estate.

Treat the headline numbers with the same care. Cycode cites more than 1.4 billion active Windows 10 and 11 devices and 14,000 "exposed" packages. I could not verify either figure, and the post does not define "exposed". It calls the flaw "critical", but it gives no CVE or CVSS vector. The Cycode page title mentions a CVSS 10.0, but the post body I reviewed does not show how that score was derived.

The fix, as visible on GitHub​

Microsoft's remediation is pull request #456300, titled "[ManualValidation] Update validation request handling". GitHub shows it merged into master on October 19, 2026, after a moderator approval and 105 passing checks. The PR description is vague: it says only that it adjusts how manual validation sends web requests. The diff to Tools/ManualValidation/ManualValidationPipeline.ps1 shows these changes:

  • No default token. Invoke-GitHubRequest no longer builds the Authorization bearer header into its default headers.
  • URI validation. The function parses the URI and rejects anything that is not a valid absolute http or https address.
  • Strict allowlist. The token is attached only if the request uses HTTPS on port 443 with no user-info in the URL. The host must also match exactly api.github.com, github.com or raw.githubusercontent.com. For any other host, the Authorization header is removed.
  • Redirect handling. The Invoke-WebRequest calls now set -PreserveAuthorizationOnRedirect:$false, so a redirect cannot carry the header elsewhere.
  • Installer status check. The inner installer-status wrapper now calls Invoke-WebRequest directly for the HEAD request, instead of the GitHub helper. That is the call Cycode's chain depended on.

The merge date is a useful detail. The fix landed about a month before Cycode's public write-up, which is consistent with the coordinated disclosure Cycode describes. Cycode thanks MSRC and the WinGet maintainers for a quick response. The public PR does not itself confirm the full exploit narrative, only that the unsafe request handling was changed.

Cycode also says a C# port of the tool already kept authorization off by default, and that the PowerShell version lacked this. I could not verify that from the sources I reviewed.

Does this affect your Windows PC?​

Based on the evidence, this was a flaw in the maintainers' internal triage tooling. It was not a flaw in the WinGet client on your machine. Nothing in the sources suggests you need a client update to address it. Nor do they show that any package you installed was tampered with.

The trust model still matters, though. As Cycode puts it, WinGet installations ultimately trust what moderators merge. One independent write-up of WinGet's design notes that manifests carry a SHA256 installer hash, which the client checks after download. That helps against a compromised publisher server. It would not help if an attacker could rewrite the manifest and its hash, which is the scenario the stolen token would have enabled.

One timing caveat: Microsoft's current repository validation documentation reportedly describes a GitHub App replacing the earlier Azure DevOps pipeline integration. So Cycode's Azure DevOps trigger should not be assumed to match today's validation flow.

Lessons for IT and engineering teams​

You don't need to run a package registry for this to apply. Any internal script that handles tokens and touches user-supplied URLs has the same risk.

  • Bind credentials to destinations. Do not let a general-purpose HTTP wrapper attach a token by default. Check scheme, host, port and user-info before adding it. Make sure redirects can't carry it to another host.
  • Treat submitted URLs as hostile. A URL in a manifest, ticket or PR can become an outbound request from a privileged workstation. Review label-triggered and background automation as closely as interactive tools.
  • Shrink the blast radius. Cycode recommends replacing Classic PATs with fine-grained tokens limited to one repository and minimal permissions. That is a recommendation, not something Microsoft has said it adopted. Public GitHub projects show the same pattern in their own release pipelines. In one, an issue notes that Classic PATs are account-wide, so documentation that treats such a token as fork-only understates what a leak could do.
  • Keep fact and hypothesis apart. The merged patch is confirmed. Exploitation, token theft and package poisoning are not.

Bottom line​

This is a well-contained example of how a supply chain weakness can come from automation. Each piece looked harmless: a label, a background loop, a helper that adds a header. Together they handed a credential to whoever controlled a URL. The fix is small, public and sensible. The "1.4 billion devices" and "14,000 packages" figures are Cycode's framing, and the evidence reviewed supports a patched vulnerability, not a known breach.

 

References

  1. (ManualValidation) Update validation request handling by Madhusudhan-MSFT · Pull Request #456300 · microsoft/winget-pkgs · GitHub github.com
  2. (ManualValidation) Update validation request handling by Madhusudhan-MSFT · Pull Request #456300 · microsoft/winget-pkgs · GitHub github.com
  3. Cycode discovers critical zero-click supply chain vulnerability in WinGet (now patched) Security Boulevard 2026-11-18T15:34:07+00:00