A critical vulnerability dubbed "GitLost" has been discovered in GitHub's Agentic Workflows, creating a serious data exposure risk for organizations utilizing the popular development platform. The flaw, which allows unauthorized access to private repository contents, represents a significant threat to the integrity of source code management and data protection strategies across countless enterprises and development teams.
The GitLost vulnerability operates through a disturbingly simple mechanism. Attackers without authentication can create a GitHub Issue within an organization's public repository. Through this seemingly innocuous action, malicious actors can then silently exfiltrate data from the organization's private repositories—repositories that should be completely inaccessible to the public. This cross-repository data leak essentially creates a bridge between public-facing and supposedly secure internal codebases, fundamentally compromising the repository isolation that organizations depend on. Any organization using GitHub's Agentic Workflows with both public and private repositories is potentially vulnerable to this exploit.
For security teams, the implications of GitLost are particularly concerning. The vulnerability undermines the foundational security principle of repository isolation, which many organizations rely on to protect sensitive code, proprietary algorithms, credentials, and other confidential information. Security professionals must now assess their exposure by identifying which private repositories might be accessible