A vulnerability in the aider CLI tool allows attackers to achieve remote code execution on a user's machine by enticing them to run aider within a malicious git repository.

The software improperly handles configuration files by automatically loading and executing commands defined in a .aider.conf.yml file located in the git repository root. This occurs without any user authentication or interaction, effectively allowing an attacker who controls the repository contents to execute arbitrary shell commands upon startup or the first file edit.

Successful exploitation of this vulnerability results in full arbitrary command execution on the host machine running the aider tool. This poses a critical risk to developers and technical staff, as an attacker could gain persistent access, exfiltrate sensitive environment variables, or compromise local development credentials. Given the CVSS score of 7.8, this vulnerability represents a high-severity threat to organizational security hygiene and workstation integrity.

Immediate Action: Cease using aider in untrusted git repositories until a patch is applied, and verify that the current installation is not operating in an environment where malicious configuration files can be introduced.

Proactive Monitoring: Monitor workstation process logs for unexpected shell subprocesses spawned by the aider process, specifically those originating from the application directory.

Compensating Controls: Implement strict directory permissions on development machines and ensure that developers are aware of the risks associated with cloning and running automated tools in repositories from untrusted sources.

Public Exploit Available: Unknown.

Users should treat this vulnerability as critical due to the potential for complete system compromise. Organizations should restrict the use of aider to trusted environments and prioritize updating the software as soon as a vendor patch is released to address the insecure configuration loading behavior.