alxsm

Good that they published an interim mitigation (TS_SSH_DISABLE_FORWARDING=1) before the full advisory instead of staying quiet until the patch. They already had an SSH issue earlier this year: in July (TS-2026-010) values passed through acceptEnv were visible to other local users via /proc and ended up in logs. Be careful when passing credentials through SSH environment variables.

What worries me is what was actually in those leaked prompts. This is a million-token context model, and people use that context to paste whole repos and configs, .env files included. So the realistic worst case isn't someone's chat text, it's someone's API keys. The write-up explains the root cause well, but doesn't say whether the customers whose prompts ended up in other people's responses were notified.

Nice guide. One problem though: with showUntrackedFiles=no, the only thing protecting you from "add -A" is habit. In a bare repo you can put a deny list in ~/.dotfiles/info/exclude (.ssh/, .aws/, .env, *.local, .zsh_history), and git will skip those files even on add -A.