Archon AI Coding Agent Has Critical Auth Bypass in Versions 0.2.13 to 0.11.1

A critical missing authentication vulnerability in the Archon AI coding agent allows unauthenticated attackers to execute commands on host systems. The flaw, tracked as CVE-2026-111322, affects versions 0.2.13 through 0.11.1 and enables remote code execution without any form of credential verification.

The National Vulnerability Database rates the severity of CVE-2026-111322 as 9.3, which is classified as critical. The weakness stems from a missing authentication control on the application's API endpoints. This specific defect is categorized under CWE-306, which describes missing authentication for critical functions within a software system.

Technical Details of the Flaw

The vulnerable component is the /api/* control API within the Archon application. By default, this API binds to the 0.0.0.0 address, making it accessible to any device on the same network segment. Attackers with network access can exploit this exposure to send arbitrary messages directly to the AI coding agent running on the host.

The AI coding agent operates with a configuration setting known as bypassPermissions. This setting allows the agent to execute commands on the host system as the Archon user. Consequently, an attacker who successfully sends a crafted message to the API can trigger command execution with the privileges of the Archon service account.

Affected Versions and Scope

The vulnerability impacts a wide range of Archon releases, specifically versions 0.2.13 through 0.11.1. Any deployment using these versions is potentially exposed if the default network binding configuration remains unchanged. The risk is present regardless of whether the application is deployed in a local or remote environment, provided network access is available.

No patch, fix, or update has been confirmed yet to address CVE-2026-111322. Users of the affected versions should assume their systems remain vulnerable until the vendor releases a remediation. The lack of authentication means that standard network segmentation may be the only immediate barrier against exploitation.

What should you do?

Security teams should immediately inventory their environments to identify any installations of Archon versions 0.2.13 through 0.11.1. If these versions are in use, organizations should restrict network access to the /api/* endpoints to prevent unauthenticated connections. Monitoring logs for unexpected command executions by the Archon user can help detect potential exploitation attempts.

What to do and how to stay safe: Archon

• Audit internal networks to locate all instances of Archon versions 0.2.13 through 0.11.1.
• Configure firewalls or network access control lists to block external access to the /api/* endpoints.
• Monitor system logs for unauthorized command executions performed by the Archon user account.
• Wait for the vendor to release an official update that addresses the missing authentication flaw.

Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger

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

Frequently asked questions

What is the CVSS score for the Archon vulnerability?

The National Vulnerability Database assigns a CVSS score of 9.3 to CVE-2026-111322, rating it as critical.

Which versions of Archon are affected by this flaw?

Versions 0.2.13 through 0.11.1 of the Archon AI coding agent contain the missing authentication vulnerability.

Is there a fix available for CVE-2026-111322?

No fix has been confirmed yet; users should monitor for vendor updates to resolve the issue.