AI Stack Alert Medium TD-2026-0055 For SOC / IR, AppSec, AI Eng, CISO Unconfirmed AI-assisted
ChatGPT Desktop reportedly forwards local SSH agent to remote machines
A Hacker News thread reports that ChatGPT Desktop forwards the user's SSH agent to remote machines. Commenters note that the linked evidence is a pull request that was closed without merging, and that the feature is described as opt-in. The source does not include the underlying technical analysis, so the forwarding behavior is not independently confirmed here.
Why it matters
If forwarding is enabled, any remote host a user connects to could use the local SSH agent to sign requests with their keys while the session is open. Hosts that are not trusted could then perform SSH actions using those keys.
Do this
- Check ~/.ssh/config and any Include files for ForwardAgent yes, and set ForwardAgent no under Host * unless a specific trusted host needs it.
- Use ProxyJump instead of agent forwarding for jump-host tunnels.
- Where possible, require a per-use approval or hardware touch for SSH key signing, for example with a hardware key or an agent that prompts on each use.
- Review ChatGPT Desktop settings and release notes for any SSH agent or forwarding option, and confirm whether it is enabled by default.
- On shared or production hosts, check for unexpected SSH agent sockets forwarded from unknown clients (for example, look for agent socket paths under /tmp or the user runtime directory).
Signals
- NoCISA KEV
- 21/100Priority
- 35%Confidence
Evidence
“This PR was closed as not merged and the entire process is described as opt-in.”
“I don't understand what the linked pull request is supposed to prove, considering it was closed and not merged.”
Sources
Affected / related
ChatGPT Desktop, OpenAI, Codex, OpenSSH ssh-agent
Published 2026-11-09 08:17 UTC · updated 2026-11-09 23:50 UTC · AI-assisted summary, checked against quoted sources · Unconfirmed: single non-official source · How we score