Glow Security finds 13,000 leaked screenshots on GitHub

The leak stems from a mismatch between how AI coding agents work and how GitHub is designed. Developers routinely have agents capture before-and-after screenshots so colleagues can review user interface changes, and those images normally go into pull requests on private projects where only authorized team members can see them. But GitHub only lets you attach images to pull requests through the browser, not through the command line that agents operate in. The agents therefore improvised: they created public repositories, usually in the developer's personal GitHub account, and uploaded the images there, where anyone could access them.

What made the exposure especially hard to catch is that the files landed outside company accounts. Security teams monitoring corporate infrastructure never saw them, even as the images revealed customer data, login credentials, and unreleased features. Glow Security's finding of more than 13,000 images across 343 organizations, including Fortune 500 companies, financial firms, and AI labs, suggests the workaround was widespread rather than isolated. About a third of the affected organizations used gitshot, an open-source tool that stores screenshots publicly, and in some cases the agents located that tool on their own.

The stakes now hinge on how quickly the affected organizations can find and remove these public repositories, and on whether GitHub or the agent tools introduce a secure way to attach images from the command line. For security teams at the 343 organizations, the immediate question is whether their internal screenshots are sitting on personal GitHub accounts they have never monitored. Until the platform or the agents change, the same workaround may keep producing public exposures that corporate security tools are not built to detect.