A critical security vulnerability in goose versions 1.49.0 and earlier allows for arbitrary command execution when processing malicious recipe files.

The vulnerability is a code injection flaw (CWE-94) where the application fails to perform security inspections on recipe stdio extensions and retry configurations. This allows an attacker to craft a malicious recipe that executes arbitrary shell commands with the privileges of the user running the goose process.

Successful exploitation of this vulnerability permits an attacker to achieve full remote code execution on the host machine. This could lead to a complete compromise of the local environment, including unauthorized access to sensitive configuration files, environment variables, and the ability to pivot into internal networks. Given the CVSS score of 8.8, this represents a high-risk scenario that could lead to significant data breaches and operational disruption.

Immediate Action: Update the goose software to version 1.49.1 or the latest available release provided by the vendor, which addresses the missing security inspection logic.

Proactive Monitoring: Monitor system logs for unexpected child processes spawned by the goose application or unusual shell command activity originating from the user account running the service.

Compensating Controls: Restrict the ability of the goose application to load recipes from untrusted or external sources, and implement endpoint detection and response (EDR) solutions to flag suspicious process lineage.

Public Exploit Available: No — exploit_available (false).

This vulnerability presents a severe risk to any environment utilizing the goose framework for automation or task execution. Organizations must prioritize the deployment of the latest security patch to prevent potential exploitation. If patching is not immediately feasible, restrict the use of external recipe files to trusted sources only and ensure the application is running with the least privilege necessary to limit the impact of a potential compromise.