News for hackers. Stuff that matters.
Re:GitLost: We Tricked GitHub's AI Agent into Leaking Privat... by siws on Wednesday July 08, 2026 @11:11AM (#48833007)
Honest question: couldn't this be solved by setting the authorization level of the agent the same as the user that prompted the question?

In this post's example, the agent would be limited by the author's scope inside the organization and, therefore, be incapable of exposing any unwanted file.

Re:GitLost: We Tricked GitHub's AI Agent into Leaking Privat... by lelanthran on Wednesday July 08, 2026 @11:57AM (#48833612)
> Honest question: couldn't this be solved by setting the authorization level of the agent the same as the user that prompted the question?

No.

> In this post's example, the agent would be limited by the author's scope inside the organization and, therefore, be incapable of exposing any unwanted file.

That still allows prompt injection to exfiltrate the authors files. That's the whole exploit - files that the author has, that he doesn't want exfiltrated.

Re:GitLost: We Tricked GitHub's AI Agent into Leaking Privat... by codethief on Wednesday July 08, 2026 @07:06PM (#48838564)
As the sibling already said, this doesn't work/help in most cases. See https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/ for a different explanation of the issue.