CVE
RedAmon missing authorization in agent session routes
Only affects RedAmon 4.0.0 before 7.8.0, where any logged-in standard-role user can see other tenants' live sessions and jobs. No vendor rating is given. Fixed in 7.8.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected: RedAmon 4.0.0 before 7.8.0 (the GHSA lists >= 4.0.0, <= 7.7.2). Attacker holds a logged-in standard-role account. Another tenant has a live Metasploit or shell session on a compromised host.
- 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? →
- 33/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? →
- Specific setups only
- 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 has a missing authorization flaw that lets an authenticated user with low privileges, reachable over the network without any user interaction, list, kill, or send commands into other tenants' agent sessions, including meterpreter and shell sessions, by supplying arbitrary session IDs. The flaw is in the agent session routes.
Original description
RedAmon 4.0.0 before 7.8.0 contains a missing object-level authorization vulnerability that allows authenticated users to control other tenants' agent sessions by supplying arbitrary session ids. Attackers can call /api/agent/sessions, interact and kill routes to list, kill, or send commands into other users' meterpreter and shell sessions on their compromised targets.
Who should check
Operators running RedAmon 4.0.0 through 7.7.2 with several standard-role users on one instance and live Metasploit sessions.
“RedAmon 4.0.0 before 7.8.0 contains a missing object-level authorization vulnerability”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure8/25Specific setups only, reachable over the network
- 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 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 40 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected: RedAmon 4.0.0 before 7.8.0 (the GHSA lists >= 4.0.0, <= 7.7.2). Attacker holds a logged-in standard-role account. Another tenant has a live Metasploit or shell session on a compromised host.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-129854 (RedAmon 4.0.0 before 7.8.0 Missing Authorization via Agent Session Routes), 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-129854 (entry last updated 2026-11-16):
Affected:
- samugit83 RedAmon: from 4.0.0, fixed in 7.8.0
Fixed versions: 7.8.0.
Conditions (all must be true for the bug to be hit):
- Affected: RedAmon 4.0.0 before 7.8.0 (the GHSA lists >= 4.0.0, <= 7.7.2). (source: https://www.vulncheck.com/advisories/redamon-4.0.0-before-7.8.0-missing-authorization-via-agent-session-routes)
- Attacker holds a logged-in standard-role account. (source: https://github.com/samugit83/redamon/security/advisories/GHSA-w454-6hwp-fm58)
- Another tenant has a live Metasploit or shell session on a compromised host. (source: https://github.com/samugit83/redamon/security/advisories/GHSA-w454-6hwp-fm58)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129854 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129854 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-w454-6hwp-fm58
- https://github.com/samugit83/redamon/releases/tag/v7.8.0
- https://github.com/samugit83/redamon/blob/b13da9cb5ad35ae75428b8f21794e799a25fd201/webapp/src/app/api/agent/sessions/%5Bid%5D/interact/route.ts#L7-L25
- https://www.vulncheck.com/advisories/redamon-4.0.0-before-7.8.0-missing-authorization-via-agent-session-routes
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-129854
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-129854"}.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
From 4.0.0 · 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-129854
Is CVE-2026-129854 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?
Any authenticated standard-role user can list other tenants' live sessions and jobs, run commands in another tenant's meterpreter or shell on that tenant's compromised target host, and kill their sessions or jobs.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-129854?
RedAmon: from 4.0.0 before 7.8.0.Source: cve.now feed data
Am I affected, and how do I check?
RedAmon versions from 4.0.0 before 7.8.0 are affected. The GHSA lists >= 4.0.0 and <= 7.7.2. Check the installed RedAmon version against that range.Source: vulncheck.com, github.com
How do I fix CVE-2026-129854?
Upgrade RedAmon to 7.8.0 or later, which is the fixed version in the affected range.Source: vulncheck.com, github.com