Quick answers
- Is CVE-2026-111079 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111079 being exploited in the wild.
- How severe is CVE-2026-111079?
- High severity, with a CVSS score of 7.4, published 22 October 2026.
- Which products and versions are affected?
- Goose.
- Is there a fix for CVE-2026-111079?
- No fixed version is recorded yet. Disable terminal integration in Goose if it is not required for your workflow, or avoid entering sensitive information such as API tokens, passwords, or credentials in the terminal when terminal integration is active. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-111079 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-111079?
- Check whether you run Goose. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Disable terminal integration in Goose if it is not required for your workflow, or avoid entering sensitive information such as API tokens, passwords, or credentials in the terminal when terminal integration is active.
Technical details
The vulnerability is an information exposure flaw (CWE-497) in Goose's terminal integration feature, which captures shell command history and transmits it verbatim to configured LLM endpoints without sanitization. The attack vector is network-based and requires user interaction—specifically, a user must enable terminal integration and execute assistant queries that include sensitive data in their command history. An attacker or malicious LLM provider can read transmitted credentials, API tokens, and environment variables.
Affected products
- Goose
Timeline
- 2026-10-22: disclosed