External risk intelligence

Eigent 0.0.60 Remote Code Execution Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2025-68952

Eigent is described as a multi-agent workforce tool. While the vulnerability allows for remote code execution, the specific deployment patterns for this product—whether used as a localized developer agent, an internal-only workflow engine, or an internet-exposed service—are not clearly established by the provided context. It is plausibly reachable in some deployments but lacks evidence of universal public exposure.

Code Injection

Eigent

0.0.60

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability in the Eigent multi-agent workforce tool allows for remote code execution with a single interaction. This means an attacker could potentially gain control of a system running the affected version of Eigent without requiring complex steps or user interaction. The issue has been addressed in a subsequent version.

Unauthenticated remote code execution is possible.
Impacts systems using a specific version of Eigent.
Confirm relevance and exposure for this tool.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by interacting with a vulnerable instance of Eigent, a multi-agent workforce tool, without needing any prior access or authentication. Successful exploitation could allow the attacker to execute arbitrary code on the affected system. This issue has since been resolved in a later version.

No prior access or authentication required.
Triggered by a specific user interaction.
Allows arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A remote code execution vulnerability in Eigent could allow an attacker to run arbitrary code on a victim's machine or server without user interaction when supported by the advisory.

Arbitrary code execution on affected systems.
Triggered through a 1-click interaction.
System compromise and data breaches.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Eigent platform's multi-agent workforce functionality is impacted by a critical RCE vulnerability. Owners of the Eigent application or the infrastructure hosting it should lead the response. The immediate priority is to locate all instances of the affected version, assess their exposure and criticality, and identify the accountable teams or individuals. A risk-based remediation plan, potentially involving vendor coordination, should then be developed and executed.

Identify Eigent 0.0.60 instances.
Verify reachability and business criticality.
Plan remediation based on risk assessment.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Eigent and how is it used?

Eigent is a software framework designed to manage multi-agent workforces. These tools typically automate complex tasks by coordinating multiple artificial intelligence agents to execute workflows, manage data, or perform actions across digital systems. Organizations utilize such platforms to streamline automated processes, though their specific role depends on whether they are integrated as localized developer utilities or deployed as backend services managing infrastructure.

What does the RCE vulnerability in CVE-2025-68952 mean?

This vulnerability is classified as CWE-94, which refers to improper control of code generation. In plain terms, the software fails to safely handle input, allowing an attacker to inject and run their own malicious commands. Because this is a Remote Code Execution (RCE) flaw, it grants an unauthorized party the ability to take control of the server or machine running version 0.0.60, effectively bypassing the software's intended operational boundaries.

How is this Eigent vulnerability triggered?

The vulnerability is triggered by a specific, single-click interaction with a vulnerable Eigent instance. It does not require the attacker to have pre-existing credentials or prior access to the system. Importantly, this bug is not triggered by idle software; it requires that interaction to initiate the malicious code execution path, making the specific interface exposure the critical factor for success.

Is my instance of Eigent at risk?

According to Halo Surface Signal, risk depends on how you have deployed the tool. While the vulnerability allows RCE, Eigent can be used as a localized developer agent or an internal workflow engine. Instances that are internet-facing face a higher likelihood of reachability for this type of attack. You should verify whether your specific deployment is accessible from external networks versus being restricted to private, internal segments.

What steps should I take if I use Eigent?

Your first step is to perform an inventory to locate all systems running version 0.0.60 of the Eigent software. Once identified, evaluate the network accessibility of these instances to determine if they are exposed. The primary resolution for this issue is to update your software, as the vulnerability has been patched in version 0.0.61. Coordinate with your team to verify the update and ensure the environment is secured.

References

github.com/eigent-ai/eigent/security/advisories/GHSA-pwcx-28p4-r…

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.