Skip to content
The Injection_
LIVE
LIVElast sweep next in--:--:--

[ RSS ][ JSON ][ llms.txt ]

RedAmon: six flaws reach root in the AI pentest framework's containers

RedAmon 7.8.0 closes six flaws that let low-privilege users reach root in the framework's agent and Kali containers.

· RedAmon · Research by Dilanka Kaushal Hewage, mappygrid, recuon

CVE-2026-129855
HIGHVulnerability

RedAmon, an open-source AI penetration testing framework, disclosed six flaws on November 14, 2026. The worst let any signed-in user run commands in the shared agent container and read its platform secrets. Version 7.8.0 fixes all six.

01What happened

RedAmon's maintainer published six security advisories on November 14, 2026, crediting Dilanka Kaushal Hewage, mappygrid and recuon. All six are fixed in version 7.8.0, released the same day. VulnCheck assigned CVE-2026-129855 and CVE-2026-129854 to two of them on November 16.

02How it works

The most severe flaw is missing authorization on the /mcp/test endpoint, which accepted a caller-supplied stdio MCP server definition and spawned the command with the agent service's own environment. A separate terminal server on port 8016 opened an interactive root bash session to any client that connected, with no token, ticket or origin check. Four agent session routes also proxied requests without checking who owned the session, so one tenant could run commands in another tenant's live Metasploit session.

03Who is affected

Multi-user RedAmon deployments from 4.0.0 through 7.7.2 are exposed, and the stdio MCP advisory states that single-user installs are not. The port 8016 terminal is published on loopback only, but the advisory notes it is reachable as kali-sandbox:8016 from the agent container and any other container on the internal Docker bridge.

04What to do

Run ./redamon.sh update to move to 7.8.0, and set the RBAC_ variables in .env first if you need any of the new switches off. Rotate the secrets the agent container held, listed below, along with any CypherFix GitHub token, and delete stdio entries from members' MCP Tool Plugins on installs you cannot patch yet.

Questions people ask

How do I upgrade RedAmon from 7.7.2 to 7.8.0?
RedAmon 7.8.0 is the fixed release, and the maintainer's documented path is ./redamon.sh update, which rebuilds the webapp, agent, Kali sandbox and recon images. Scans running during the restart may fail and need restarting. The release turns RBAC switches on by default, so set RBAC_IDENTITY_ENABLED or its siblings to false in .env beforehand if you need them off.
Am I affected by the RedAmon stdio MCP flaw if I am the only user?
Single-user RedAmon installs are not exposed to GHSA-j3r5-x2gg-2hgv, according to the advisory, because the flaw needs a second signed-in account holding the standard role. Multi-user deployments with MCP Tool Plugins enabled are exposed. The separate port 8016 terminal flaw does not depend on how many accounts exist, so a single-user install still needs 7.8.0.
Which of the six RedAmon flaws have CVE numbers?
VulnCheck published CVE-2026-129855 for the unauthenticated terminal PTY WebSocket on port 8016 and CVE-2026-129854 for the missing authorization on agent session routes, both on November 16, 2026. The other four advisories, including the critical stdio MCP command execution rated CVSS 9.9, carry GHSA identifiers only and are recorded as having no known CVE.
What should I rotate after patching RedAmon?
Rotate every secret the RedAmon agent container could read. The critical advisory names INTERNAL_API_KEY, DATABASE_URL and NEO4J_PASSWORD, and a related report says the scanner key could also read a project's stored GitHub personal access token in full. LLM provider keys added at /settings belong on the same list, since a shell in the agent process reads its environment.
How does this compare to the earlier RedAmon terminal CVE?
CVE-2026-103015 was an earlier fix that added bearer-token middleware to RedAmon's SSE MCP tool servers. GHSA-3cjg-8cp8-j269 explains that the fix was incomplete, because the port 8016 listener is a separate websockets.serve instance that never used that middleware. A root bash session therefore stayed open to any client that could reach the port.

Sources 7 links, all fetched

  1. 1github.comRedAmon 7.8.0 Release
  2. 2github.comStdio MCP Advisory
  3. 3github.comRoot Shell Advisory
  4. 4github.comSession Hijack Advisory
  5. 5github.comRoot Command Advisory
  6. 6github.comApproval Bypass Advisory
  7. 7vulncheck.comVulnCheck CVE Advisory