A critical prompt injection flaw in GitHub Agentic Workflows allows attackers to trick AI-powered automation into leaking data from an organization's private code repositories, all without compromising an account or exploiting software vulnerabilities. Using the flaw, dubbed "GitLost" by the researchers from Noma Security who discovered it, an unauthenticated attacker can craft a GitHub Issue in a public repository belonging to an organization, and then silently pull data from its private repositories, too, according to a report published yesterday. GitHub Agentic Workflows pairs GitHub Actions — the platform's automation system for running tasks in response to repository events — with an AI agent backed by Claude or GitHub Copilot to help developer teams manage their GitHub workflows. The tool lets teams automate their interactions with code repositories using natural language, and the GitHub agent can read issues, call tools, and access other repositories within an organization. "GitLost perfectly illustrates one of the fundamental security challenges every organization faces with agentic AI systems," Sasi Levi, security research lead at Noma, wrote in the report. "The agent's context window is also its attack surface. Any content the agent reads, whether issues, pull requests, comments, or files, can be weaponized if the agent treats that content as instructional input." This scenario paved the way for what has now become a common attack vector in agentic AI systems: promp...
'GitLost' Flaw Leaks Private Data From GitHub's Agentic Workflows
Dark Reading
·Elizabeth Montalbano
·Published Jul 7, 2026
·Updated
Affected Software
1 affected component
GitHub Agentic Workflows
Frequently Asked Questions
1
What is the main topic of this article?
The article discusses a critical prompt injection flaw in GitHub Agentic Workflows, known as 'GitLost', which can leak private data.
2
What security implications are discussed in the article?
The flaw allows attackers to exploit AI-powered automation to access sensitive information without needing to compromise accounts or software vulnerabilities.
3
What products or software are affected by the flaw?
The affected product is GitHub Agentic Workflows.
4
When was the 'GitLost' flaw first reported?
The 'GitLost' flaw was first reported on July 7, 2026.
5
When is the exploitation of this flaw expected to be publicly listed?
The exploitation of this flaw is KEV-listed for July 9, 2026.