News for hackers. Stuff that matters.

A comment on GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos. Parent comment

Re:GitLost: We Tricked GitHub's AI Agent into Leaking Privat... by coldtea on Wednesday July 08, 2026 @05:31AM (#48829699)
It's not about if it can happen or if it happens.

It's about how easily it's mitigated completely. Use a proper db library which does escaping and it's completely eliminated.

[ Parent | on HN ]
Re:GitLost: We Tricked GitHub's AI Agent into Leaking Privat... by brookst on Wednesday July 08, 2026 @08:33AM (#48831121)
Nit: modern DB libraries use wire protocols where SQL injection is mitigated by modeling parameters; it’s not just assembled to one big SQL statement and escaped.

Agree with your point though. There will come a time when properly designed LLM apps are not vulnerable, and there will still be poorly designed apps that are.

[ Parent | on HN ]
Re:GitLost: We Tricked GitHub's AI Agent into Leaking Privat... by macintux on Wednesday July 08, 2026 @05:51PM (#48837894)
> There will come a time when properly designed LLM apps are not vulnerable, and there will still be poorly designed apps that are.

Whether it’s possible to properly secure an LLM (and retain its utility) seems to be heavily disputed, in this thread and elsewhere.

[ Parent | on HN ]
Re:GitLost: We Tricked GitHub's AI Agent into Leaking Privat... by silon42 on Tuesday July 14, 2026 @08:26AM (#48905735)
Yes, if SQL statements would be replaced by a restricted object model, SQL injection is by definition impossible. But you can just "prompt inject" the LLM itself.
[ Parent | on HN ]