Skip to content

AAK-MCP-TRINITY-CVE-2026-108756-001: Trinity backend image through 0.9.5: an agent's MCP key can replace or delete its owner's Telegram binding (no fixed release)

Severity
MEDIUM
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/container_image_pins.py
Auto-fixable
No.
SARIF name
TrinityTelegramBindingAgentKeyBypass

What it detects

Trinity (Abilityai/trinity) is a self-hosted agent platform whose backend ships as ghcr.io/abilityai/trinity-backend. An agent-scoped MCP API key resolves to the agent's owner, and the Telegram router's binding routes (configure_telegram_bot and delete_telegram_binding in src/backend/routers/telegram.py) check only that the caller owns the agent, with no reject_agent_principal. So an agent, typically steered by prompt injection, can perform what are meant to be human-only binding operations: in NVD's words, "send messages through the owner's bot token, replace the binding with their own token, or delete it" (CVE-2026-108756, CVSS 3.1 5.4, CWE-862). The images start at 0.9.5-rc1, 0.9.5 is the newest release, and the 1.0.0 release candidates still serve those routes without the check, so there is no fixed release.

How to fix

There is no fixed release. Until one ships, treat every agent on an instance with a Telegram binding as able to change that binding: remove the binding from agents that do not need it, and check the bound bot after any agent run that read untrusted content. Pin the first fixed release once it ships.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-TRINITY-CVE-2026-108756-001

Limitations

Reads ghcr.io/abilityai/trinity-backend references up to and including 0.9.5, and latest, which was the 0.9.5 digest on 2026-10-13, in compose files, Kubernetes manifests, Helm values, Dockerfiles and MCP configs. Trinity's own compose files build the backend from source or name it with ${TRINITY_IMAGE_TAG:-latest}, which states no version this reader trusts, so such an instance is reported only where a manifest states the tag. The 1.0.0 release candidates read as 1.0.0 and are not reported, although they still lack the check, and the two-part 0.9 tag floats and is not reported.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-TRINITY-CVE-2026-108756-001.md: the page then shows that text, with the registry reference appended under it.