CVE-2026-129854 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
RedAmon before 7.8.0 does not check object-level ownership on its agent session routes, so an authenticated user can supply another tenant's session id. An attacker can then list, kill, or send commands into other users' meterpreter and shell sessions.
first public Nov 14, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that run RedAmon 4.0.0 through versions before 7.8.0 with more than one tenant or user sharing an instance. Single-user deployments with no other users on the platform are less exposed. The sources do not say which deployments are multi-tenant by default.
Not affected if single-user, version-7.8.0-or-later
Who cares multi-tenant, redamon, self-hosted
7.8.0 are affected./api/agent/sessions and the interact and kill routes for session ownership checks.7.8.0 or later, per the release notes and the product range.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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.