Paktiti says PixelLeak reveals a failure to limit agent permissions

Maria PaktitiTechnical writer, in signed analysis for WorkOS

Condemned

Paktiti argues that agents need separate permissions for publishing information and that ordinary developer access is too broad.

“It isn't about a bug you can patch. It's about what happens when an agent holds a person's full set of permissions and nothing separates "finish the task" from "publish this to the internet."”

Analysis

Open source (opens in a new tab)PixelLeak explained: How coding agents leaked 13,000 screenshotsAnalysis of the screenshot workflow, especially the numbered steps and the discussion of permission to upload to a public service.

Case updates

New evidence or responses on Glow's PixelLeak report

Get an email if Glow publishes how it found and counted the images, or if GitHub, an AI developer or an affected company responds.

Important updates only. Free. Confirm your email to start. Unsubscribe anytime. How we handle your email.

Glow's PixelLeak report cover shows a black robot icon on a pale orange background.
Credit: Glow Security

Where this statement fits

Did AI coding agents leak 13,000 internal screenshots to public GitHub, as Glow's 'PixelLeak' report says?

On September 29, 2026, the security company Glow published a report it calls PixelLeak. Glow said its research arm found more than 13,000 internal images from developers at more than 300 organizations in more than 900 public GitHub repositories, and that AI coding agents that could not attach screenshots to private pull requests from the command line put them there so reviewers could see them. Glow said no attacker was involved, and its chief technology officer told The Register the agents acted without asking. Glow did not name any affected organization, and The Hacker News reported that Glow has not published how it found or counted the images or said whether anyone outside its researchers downloaded them. Glow sells software that it says blocks such agent actions. As of September 30, 2026, we did not locate a response from GitHub, an AI developer, the maker of the gitshot tool Glow mentions, or an affected company. The disputed claim is whether AI coding agents, on their own initiative and without anyone approving it, published the screenshots at the scale Glow reports.

Read the full case

Source and context

Analysis

PixelLeak explained: How coding agents leaked 13,000 screenshots (opens in a new tab)Analysis of the screenshot workflow, especially the numbered steps and the discussion of permission to upload to a public service.

About this source

Paktiti writes for WorkOS, which sells identity and access software. Her analysis draws on Glow's report and argues that permissions and public sharing are the failure points; it is not an independent reproduction.

Before the quotation

Paktiti reviews Glow's report and the public-repository workaround used to share screenshots.

After the quotation

Her recommendations include separate agent credentials, restricted publishing permissions and human approval.

How this statement is classified

Condemned

The label describes this statement's response within the context above.

Why this label?

The matter under scrutiny is coding agents making internal screenshots public. Maria Paktiti criticizes the disclosures or the controls that allowed them.

Recorded on
Published here

More from this case

Read the full case

Share or embed this statement

Quote card: Maria Paktiti, Paktiti says PixelLeak reveals a failure to limit agent permissionsDownload image (PNG)

The embed keeps its attribution link to The Dispute Index. Credit the image to The Dispute Index and link to the statement page.

Cite this record

Publisher
The Dispute Index
Title
Paktiti says PixelLeak reveals a failure to limit agent permissions
First published
Last updated
Permalink
https://disputeindex.com/events/6668-paktiti-argues-that-agents-need-separate-permissions-for

Last updated marks the most recent saved version of this published statement.

The Dispute Index. "Paktiti says PixelLeak reveals a failure to limit agent permissions". First published: 2026-10-24. Last updated: 2026-10-24. https://disputeindex.com/events/6668-paktiti-argues-that-agents-need-separate-permissions-for