CVE-2026-108756
Description
Abilityai Trinity through 0.9.5 contains a missing authorization vulnerability in the Telegram router that allows agent-scoped MCP API keys to perform human-only binding operations. Attackers controlling an agent, typically via prompt injection, can send messages through the owner's bot token, replace the binding with their own token, or delete it.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://github.com/Abilityai/trinity
- https://github.com/Abilityai/trinity/blob/e38c1c0f2567c602541c90c4c92152e99e6ead11/src/backend/routers/telegram.py#L168-L219
- https://github.com/Abilityai/trinity/blob/e38c1c0f2567c602541c90c4c92152e99e6ead11/src/backend/routers/telegram.py#L258-L323
- https://hackmd.io/@haind/rJ2OBa8sfl
- https://www.vulncheck.com/advisories/abilityai-trinity-through-0.9.5-missing-authorization-in-telegram-binding-routes
CWEs
CWE-862
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.