LIVE · cybersecurity feed
Live wire
vulnerability

Malicious .git Configs Can Make Claude, Codex, Cursor, and Other AI Agents Run Attacker Code

Manifold Security has reported the discovery of eight security vulnerabilities across seven distinct command-line AI coding agents. The core mechanism of these flaws involves a malicious Git configuration file within a repository, which can instruct the AI agent to execute an arbitrary command on the developer's machine. Four of these identified vulnerabilities remain unpatched at the time of…

ZeroDay News ·

Source: The Hacker News

Manifold Security has reported the discovery of eight security vulnerabilities across seven distinct command-line AI coding agents. The core mechanism of these flaws involves a malicious Git configuration file within a repository, which can instruct the AI agent to execute an arbitrary command on the developer's machine. Four of these identified vulnerabilities remain unpatched at the time of the report's publication.

The reported vulnerabilities leverage the way certain AI coding agents interact with Git repositories. Specifically, a repository's `.git/config` file can be crafted to specify a command that the agent then executes. This execution occurs with the privileges of the user running the agent and bypasses any sandboxing mechanisms the agent might employ. Furthermore, the execution proceeds without requiring an explicit approval prompt from the user, making the attack potentially stealthy.

For successful exploitation, the malicious repository must be introduced to the developer's system. This typically implies that the developer either clones a repository containing the malicious configuration or initializes a repository from untrusted sources. Once the repository is present and the AI agent interacts with it in a manner that triggers the Git configuration, the embedded command is executed.

The affected AI agents include those from prominent developers such as Claude, Codex, and Cursor, among others. Products in this category are designed to assist developers by automating coding tasks, generating code, or providing intelligent suggestions. Their integration with version control systems like Git is a common feature, enabling them to operate directly within a developer's workflow.

Mitigation for this class of vulnerability generally involves exercising caution when interacting with untrusted repositories. Developers should avoid cloning or initializing Git repositories from unknown or unverified sources. Additionally, security best practices suggest reviewing the contents of `.git/config` files, especially in new or unfamiliar repositories, before allowing AI agents or other tools to interact with them. Vendors of AI agents are also expected to implement more robust parsing and execution policies for Git configurations, potentially by disallowing arbitrary command execution or by introducing explicit user prompts for such actions.

This discovery highlights a broader security concern at the intersection of AI development tools and established software development practices. As AI agents become more deeply integrated into the development lifecycle, the potential for novel attack vectors that exploit the trust placed in these tools and their underlying infrastructure increases. It underscores the ongoing need for rigorous security auditing of AI-powered development tools and for developers to maintain vigilance regarding the provenance of their code and development environments.

vulnerabilitypatchaicloud
ShareXLinkedInWhatsAppFacebook

More News

view all →
security

Canadian cybersecurity executive arrested in federal extortion case

A Canadian cybersecurity executive was arrested in Pennsylvania on Thursday, facing federal charges of conspiracy to commit extortion. Edward Dubrovsky, 54, a co-founder and former Chief Operating Officer of CYPFER, a firm specializing in ransomware negotiation, is charged with conspiring to threaten the confidentiality of information for extortion and conspiring to commit Hobbs Act extortion,…

breach

Criminal IP Introduces AITEM as the Next Evolution of Attack Surface Management

AI SPERA, the company behind the cyber threat intelligence platform Criminal IP, has announced AITEM (AI-Powered Threat Exposure Management), an expansion of its Attack Surface Management (ASM) offerings. AITEM aims to move beyond traditional asset discovery to provide a more comprehensive approach to understanding, prioritizing, and responding to security exposures. The platform is scheduled…

ai

AI Is Getting Really Good at Messing With Cybercriminals

Anti-cybercrime initiatives are increasingly deploying artificial intelligence to disrupt scammers by engaging them with lifelike bots, which the criminals mistake for genuine victims. This strategy aims to waste scammers' time and resources while gathering intelligence on their operations.

ransomware

FBI Arrests Ransomware Negotiation Firm Co-Founder in ShinyHunters Probe

The Federal Bureau of Investigation (FBI) has reportedly arrested Edward Dubrovsky, a co-founder of the ransomware negotiation firm Cypfer and currently associated with CyberSteward. The arrest is said to be part of the ongoing ShinyHunters investigation, specifically in connection with an incident involving FBI job applicant data.

ai

The Third-Party Agent Problem: Why Security Built for AI You Chose Misses the Agents You Didn't

A new report highlights a significant blind spot in enterprise security architectures concerning the proliferation of third-party AI agents. The forthcoming 2026 State of Agent Security Report indicates that current security models, often designed to protect AI systems directly chosen and deployed by an organization, frequently fail to account for AI capabilities embedded within third-party…

security

Insider Cyber Extortion Plot Against Industrial Firm Lands Engineer in Prison

A former core infrastructure engineer has been sentenced to prison for an attempted cyber extortion plot against an industrial firm. The engineer reportedly deleted administrative accounts and reset hundreds of user passwords, subsequently demanding a ransom of 20 Bitcoin to prevent further disruption to the company's servers.