Skip to content
Vulnerabilities

Unauthenticated Access in Archon AI Agent Exposes Host Command Execution

A critical flaw in Archon versions 0.2.13 to 0.11.1 allows network attackers to execute commands as the Archon user without credentials.

Illustration: A sleek black server node sits isolated in a dark room.
AI-generated illustration: AppSec Scoop

Key points

  • CVE-2026-111322 affects Archon versions 0.2.13 through 0.11.1 with a CVSS score of 9.3.
  • The vulnerability enables unauthenticated access to the control API, which binds to 0.0.0.0 by default.
  • Attackers can send messages to the agent to execute host commands with bypassPermissions enabled.

A critical authentication bypass in the Archon AI coding agent allows unauthenticated network attackers to execute arbitrary commands on the host system. This vulnerability affects versions 0.2.13 through 0.11.1 and carries a CVSS score of 9.3, rated as critical by the National Vulnerability Database.

What happened

The National Vulnerability Database record for CVE-2026-111322 identifies a missing authentication weakness within the Archon software. Specifically, versions 0.2.13 through 0.11.1 are affected by this flaw. The issue stems from the /api/* control API endpoint, which is configured to bind to 0.0.0.0 by default. This default configuration exposes the interface to any entity with network access to the host.

An attacker does not require valid credentials to interact with this endpoint. According to the NVD description, an unauthenticated adversary can send messages directly to the AI coding agent. The agent is configured to run with bypassPermissions, a setting that removes standard execution restrictions. Consequently, the attacker can instruct the agent to execute commands on the underlying host system. These commands run with the privileges of the Archon user account.

Why it matters

The severity of this issue is driven by the combination of network exposure and elevated privileges. The default binding to 0.0.0.0 means the service is accessible from any interface, not just localhost. This eliminates the need for local access or credential theft. The ability to execute commands as the Archon user allows an attacker to perform actions that the user account is permitted to do.

The use of bypassPermissions further reduces the barrier to successful exploitation. Standard permission checks that might block certain operations are effectively disabled for the agent. This creates a direct path from a network-level interaction to host-level command execution. Security teams must treat this as a high-risk exposure because it requires no initial foothold or authentication. The critical CVSS rating reflects the ease of exploitation and the significant impact on system integrity.

What happens next

No patch or fix has been confirmed by the vendor yet. Teams must assume the vulnerability is present in all installations of versions 0.2.13 through 0.11.1. Immediate action should focus on limiting network access to the affected API endpoints. Organizations should verify if the service can be bound to localhost only. Monitoring for unusual command execution from the Archon user account is also advised.

Patch priority

Security teams should prioritise systems exposed to untrusted networks for immediate isolation. Check whether the Archon service is running on public-facing interfaces or internal segments with broad access. If possible, restrict network access to the API endpoint using firewall rules or security groups. Validate that the service binds only to localhost if remote access is not required. Test any network segmentation changes in a non-production environment first. Back up configuration files before making changes. Monitor logs for any signs of unauthenticated API calls or unexpected command executions from the Archon user.

What to do and how to stay safe: Archon

  • Restrict network access to the Archon API endpoint to trusted internal IPs only, or bind the service to localhost if remote access is unnecessary.
  • Implement network segmentation to isolate systems running vulnerable Archon versions from untrusted networks and general corporate traffic.
  • Monitor system logs for unauthenticated requests to the /api/* endpoint and for unusual command executions initiated by the Archon user account.
  • Verify that the bypassPermissions setting is necessary for your specific use case and consider removing it if it increases unnecessary risk.

Step-by-step guide: Patch Management: Definition, Purpose and Operational Reality

General security guidance from the AppSec Scoop newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

Which versions of Archon are affected by CVE-2026-111322?

Versions 0.2.13 through 0.11.1 are affected by this missing authentication vulnerability.

Is there a patch available for this vulnerability?

No fix has been confirmed yet by the vendor.

How can an attacker exploit this vulnerability?

An attacker can send messages to the AI coding agent via the unauthenticated /api/* endpoint to execute commands on the host.

Sources

  1. NVD
ArchonCVE-2026-111322NVDAI coding agentauthentication bypass

Related stories