CVE-2026-111079: Goose terminal integration sends your unredacted shell history, including secrets, to the LLM provider
With Goose's terminal integration (goose term init) set up, Goose recorded the commands you typed and sent them verbatim, with no redaction, to the configured LLM provider when you asked @goose something. API tokens, passwords or exported secrets typed in that terminal left the machine and could end up in provider logs. Red Hat rates it Important and shipped fixed goose 1.45.0-2 packages for RHEL 9.8 and 10.2 on 5 November 2026. Current upstream Goose no longer records commands by default: history capture is opt-in via --dangerous-include-history.
What it is
The terminal integration adds a shell hook that logs each command; when you query the assistant, the logged commands are included in the request to the LLM endpoint without sanitisation (CWE-497).
Anything typed as a command argument or export, such as bearer tokens, API keys or passwords, is sent across the trust boundary to the model provider and may be logged or retained there.
Red Hat's statement: it needs the terminal-integration subshell to be set up and an assistant query; normal non-interactive CLI use and sessions without the terminal hook are not affected.
Fixed packages: goose-1.45.0-2.el9_8 (RHSA-2026:95723) and goose-1.45.0-2.el10_2 (RHSA-2026:95724). Red Hat doesn't name an upstream release. The current Goose docs say history capture is off by default and only enabled with --dangerous-include-history, which warns that credentials on command lines go to the model provider.
How to check
- Look in ~/.zshrc, ~/.bashrc, fish/nushell config or your PowerShell $PROFILE for a `goose term init` line, and whether it has --dangerous-include-history.
- On RHEL or Fedora, run `rpm -q goose` and compare with 1.45.0-2.
- Think back over secrets you typed in a hooked terminal before asking @goose a question.
How to fix
- Install the patched distro package (goose 1.45.0-2 on RHEL 9.8/10.2 and Fedora) or update Goose to a current upstream release, where history capture is opt-in.
- Don't use --dangerous-include-history in terminals where you handle secrets; on an older build, remove the goose term init line until you update.
- Rotate any token or password typed in a hooked terminal before a Goose query, and pass secrets via files or a secret manager instead of command lines.
rpm -q goose 2>/dev/null; goose --version
grep -n 'goose term init' ~/.bashrc ~/.zshrc ~/.config/fish/config.fish 2>/dev/null