CVE
RedAmon unauthenticated root shell in terminal PTY WebSocket
RedAmon 7.7.2 and earlier, where the terminal PTY WebSocket server listens on port 8016, is affected. Fixed in 7.8.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 7.8.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 7.8.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
RedAmon's kali-sandbox terminal server accepts connections on its WebSocket listener without requiring authentication. An attacker in an adjacent position, such as a co-resident container or the host loopback, can connect without logging in and run commands as root inside the kali-sandbox container.
Original description
RedAmon before 7.8.0 contains a missing authentication vulnerability in the kali-sandbox terminal server that allows unauthenticated attackers to obtain a root shell by connecting to its WebSocket listener on port 8016. Attackers who can reach the port from co-resident containers or the host loopback can send keystrokes to an interactive /bin/bash session, executing commands as root inside the kali-sandbox container.
Who should check
Teams running RedAmon 7.7.2 or earlier, especially hosts exposing the kali-sandbox container on the Docker bridge or host port 8016
“Affecting RedAmon >= 0, < 7.8.0”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure?/25Unknown. Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.7/10CVSS 8.7, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 7.8.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129855 (RedAmon before 7.8.0 Unauthenticated Root Shell via Terminal PTY WebSocket), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129855 (entry last updated 2026-11-16):
Affected:
- samugit83 RedAmon: fixed in 7.8.0
Fixed versions: 7.8.0.
Conditions (all must be true for the bug to be hit):
- RedAmon 7.7.2 and earlier, where the terminal PTY WebSocket server listens on port 8016 (source: https://github.com/samugit83/redamon/security/advisories/GHSA-3cjg-8cp8-j269)
- Attacker must reach port 8016 via the internal Docker bridge or the host loopback-published port (source: https://github.com/samugit83/redamon/security/advisories/GHSA-3cjg-8cp8-j269)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-129855 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129855 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/samugit83/redamon/security/advisories/GHSA-3cjg-8cp8-j269
- https://github.com/samugit83/redamon/releases/tag/v7.8.0
- https://github.com/samugit83/redamon/blob/b13da9cb5ad35ae75428b8f21794e799a25fd201/mcp/servers/terminal_server.py#L57-L72
- https://www.vulncheck.com/advisories/redamon-before-7.8.0-unauthenticated-root-shell-via-terminal-pty-websocket
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129855
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129855"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- samugit83 RedAmon
fixed in 7.8.0
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129855
Is CVE-2026-129855 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The terminal PTY WebSocket server forks an interactive /bin/bash for any WebSocket client without authentication. Any client that can reach the port gets a shell, which runs as root in the shipped kali-sandbox container.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-129855?
RedAmon: before 7.8.0.Source: cve.now feed data
Am I affected, and how do I check?
RedAmon versions before 7.8.0 are affected, where the terminal PTY WebSocket server (mcp/servers/terminal_server.py) listens on port 8016. A reader can check their installed RedAmon version and whether that server listens on port 8016, and whether that port is reachable over the internal Docker bridge (kali-sandbox:8016) or a loopback-published host port.Source: github.com, vulncheck.com
How do I fix CVE-2026-129855?
Upgrade RedAmon to version 7.8.0 or later. The facts name no vendor patch ids or workaround.Source: github.com, vulncheck.com