Skip to content
AgentProv

2026-07-07 · 2026-Q3

"GitLost" Leaks Private Repositories via GitHub Agentic Workflows

Who actually said "do this"?

The question layer 2 asks, and failed here.
Fixable
Architectural
Vendor response
Not a vulnerability
In the wild
No
Actor
Attacker

Target

GitHub Agentic Workflows (public preview; agents running on Copilot, Claude, Gemini, or Codex inside GitHub Actions)

Impact

An unauthenticated attacker files a public GitHub issue containing hidden plain-English instructions; when the workflow triggers, the credentialed agent (which can read repositories the attacker cannot) follows them and posts private repository contents into a public comment. The proof of concept exfiltrated a private repo's README into a public comment, and prefixing the injection with "Additionally" bypassed GitHub's threat-detection guardrails

Root cause

The agent cannot distinguish owner instructions from attacker-planted content in an untrusted issue (the "lethal trifecta" of private-data access, untrusted input, and a public output channel); GitHub describes it as an architectural limitation rather than a patchable bug. Found by Noma Security

Sources

Catalog

Cite this: AgentProv incident record: "GitLost" Leaks Private Repositories via GitHub Agentic Workflows (2026-07-07). https://agentprov.com/incidents/2026-07-07-gitlost-leaks-private-repositories-via-github-agentic-workflows