Live › vulnerability › CVE-2026-119664
Tamery (formerly Conar) versions 0.26.1 before 0.99.0 have an authorization flaw in the cloud sync chatsMessages.update handler, which accepts a client-supplied chatId without checking ownership. An authenticated Pro subscriber who knows another user's chat ID can insert messages with arbitrary parts and metadata into the victim's AI chat history.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 15:31 UTC. All times on this page are UTC.
Users of Tamery's cloud sync feature on affected versions, where a Pro subscriber account is needed to exploit the flaw. Installations on version 0.99.0 or later, or without cloud sync use, are not exposed according to the description. Whether self-hosted deployments are included is unknown.
No product ranges from the sources yet.
0.99.0.0.99.0 or later, per the affected range stated in the source.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Tamery (formerly Conar) 0.26.1 before 0.99.0 contains an authorization bypass vulnerability in the cloud sync API chatsMessages.update handler, which leaves the client-supplied chatId writable. Authenticated Pro subscribers who know another user's chat ID can move messages with arbitrary parts and metadata into the victim's AI chat history.
This page as .md · .json · in your agent: get_signal("CVE-2026-119664")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.