Archon AI Remote Code Execution Flaw Affects Versions 0.2.13 to 0.11.1
Unauthenticated access to the Archon AI coding agent API allows remote attackers to execute commands on the host system without credentials.
Key points
- CVE-2026-111322 affects Archon versions 0.2.13 through 0.11.1 with a CVSS score of 9.3.
- The vulnerability allows unauthenticated network access to the /api/* control interface.
- Attackers can leverage the agent's bypassPermissions setting to run commands as the Archon user.
Remote attackers with network access to the Archon AI coding agent can execute arbitrary commands on the host system. This capability stems from a missing authentication vulnerability in the application's control API. The flaw grants unauthenticated users the ability to send messages to the agent, which operates with elevated permissions. Consequently, adversaries gain command execution rights as the Archon user without needing valid credentials.
How it unfolded
- The vulnerability exists in Archon versions 0.2.13 through 0.11.1, according to the National Vulnerability Database.
- The /api/* control API binds to 0.0.0.0 by default, exposing it to network traffic.
- Attackers send messages to the AI coding agent via this unauthenticated interface.
- The agent executes commands on the host system using its bypassPermissions configuration.
Who is affected
Organizations using Archon AI coding agent versions between 0.2.13 and 0.11.1 are affected by this issue. The vulnerability is rated critical with a CVSS score of 9.3. Any system where the Archon service is accessible over the network is at risk. Attackers only need network access to exploit the missing authentication controls on the API endpoints.
The fix
No patch or update has been confirmed for this vulnerability yet. Users should monitor official channels for vendor guidance. Until a fix is available, limiting network access to the service is the primary mitigation strategy. Ensure that the /api/* endpoints are not reachable from untrusted networks.
What made it possible
This scenario illustrates the risk of exposing management interfaces without strict access controls. Teams usually secure APIs behind authentication layers to prevent unauthorized command execution. When services bind to all network interfaces by default, they increase the attack surface significantly. Check whether your deployment restricts API access to trusted internal networks only. Verify that administrative functions require explicit identity verification before processing requests.
What to do and how to stay safe: Archon
- Restrict network access to the Archon API endpoints to trusted internal subnets only.
- Monitor logs for unauthorized message submissions to the AI coding agent interface.
- Ensure the service does not bind to 0.0.0.0 if external access is not required.
- Wait for the vendor to release an official update addressing CVE-2026-111322.
Step-by-step guide: What Is Virtual Patching: How It Works Without Code Changes
General security guidance from the RedTeam Tribune newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Which versions of Archon are vulnerable to this authentication bypass?
Archon versions 0.2.13 through 0.11.1 are affected by CVE-2026-111322, according to the NVD record.
What can an attacker do with this vulnerability?
Attackers can execute commands on the host system as the Archon user without authentication.
Is there a fix available for CVE-2026-111322?
No fix has been confirmed yet; users should monitor for vendor updates.
