CVE-2026-10222 in hermes-agentinfo

Summary

by MITRE • 06/01/2026

A security flaw has been discovered in NousResearch hermes-agent up to 2026.4.30. Affected by this issue is the function _sanitize_env_lines of the file hermes_cli/config.py. The manipulation results in injection. It is possible to launch the attack remotely. The attack requires a high level of complexity. The exploitation is known to be difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 06/01/2026

The security vulnerability identified in NousResearch hermes-agent version 2026.4.30 represents a critical injection flaw within the application's configuration handling mechanism. This vulnerability exists in the _sanitize_env_lines function located in hermes_cli/config.py, which processes environment variable configurations during application initialization. The flaw stems from inadequate input validation and sanitization of environment variable lines, creating a pathway for malicious actors to inject arbitrary commands or data into the application's execution flow. The vulnerability's remote exploitability means that attackers can potentially compromise systems without requiring physical access or local privileges, making it particularly dangerous in networked environments where the application may be exposed to untrusted inputs.

The technical nature of this vulnerability aligns with common injection attack patterns that fall under CWE-74, which describes "Improper Neutralization of Special Elements in Output Used by a Downstream Component." The flaw allows for command injection attacks where malicious environment variables can be crafted to execute unintended system commands or manipulate application behavior. The high complexity requirement for exploitation suggests that while the vulnerability exists, attackers must overcome additional technical barriers to successfully leverage it, potentially involving multi-step attack chains or specific environmental conditions. However, the fact that public exploits have been released indicates that the attack vectors have been sufficiently documented and refined to be accessible to a broader range of threat actors.

The operational impact of this vulnerability extends beyond simple command execution, as it could potentially allow attackers to gain unauthorized access to system resources, escalate privileges, or manipulate application configurations to redirect traffic or compromise data integrity. The vulnerability's presence in a configuration processing function means that successful exploitation could affect the application's core functionality and security posture. Given that the vendor did not respond to early disclosure attempts, organizations utilizing this software are left without official patches or mitigations, creating a window of opportunity for malicious actors to exploit the flaw. The vulnerability's classification as a remote attack vector means that systems may be compromised from external networks, potentially affecting cloud deployments, containerized environments, or applications exposed to public internet access.

Organizations should immediately implement defensive measures including network segmentation to limit access to affected systems, monitoring for unusual environment variable usage patterns, and implementing input validation at multiple layers of their security infrastructure. The lack of vendor response underscores the importance of proactive security measures and the potential need for third-party patches or alternative solutions. Security teams should also consider the potential for this vulnerability to be leveraged in broader attack campaigns, particularly in environments where multiple applications may be configured using similar patterns, potentially creating cascading effects across interconnected systems. The vulnerability's exploitation difficulty does not negate the need for immediate action, as the availability of public exploits increases the risk profile significantly.

Responsible

VulDB

Disclosure

06/01/2026

Moderation

accepted

CPE

ready

Exploit

Download

EPSS

0.00266

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!