@losttourist@social.chatty.monster
2026-09-24 06:58 UTC
@gerikson@awful.systems @rmf@awful.systems Yeah I don't see how this is a vuln that specifically targets LLMs rather than just git users in general. If the vulnerable command is git checkout BLAH because BLAH has been poisoned from a SHA to a ref, that's going to affect anyone or anything that issues that command, human or machine, surely?
Replies (1)
-
@rmf@awful.systems 2026-09-24 12:44
humans are unlikely to issue checkout commands with commit IDs, plus git does issue a warning when a ref name is ambiguous like this. So that leaves mostly automated stuff. But lots of things that rely on git behind the scenes don’t just go out and invoke the git binary, they use something like libgit2 and (depending on programming language) this interface will have type checks that prevent treating a commit ID as a ref name. This is why LLMs are more likely to fall into this than other software, because it’s all ducktaped together.