CVE-2026-119664

Tamery (Conar) 0.26.1 before 0.99.0 Authorization Bypass via chatsMessages.update

Published Oct 30, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Tamery (formerly Conar) versions 0.26.1 up to but not including 0.99.0 possess a flaw in the cloud‑sync API endpoint chatsMessages.update. The flaw allows an authenticated Pro subscriber to set the chatId field on a request, thereby re‑assigning a message to an arbitrary chat. An attacker who knows the identifier of another user’s chat can move messages with any content or metadata into that user’s AI chat history, effectively hijacking or overwriting that user’s conversation data. This constitutes an authorization bypass that gives an attacker unauthorized ownership over a chat and potentially sensitive data that the victim thought was private.

Affected Systems

The vulnerability is confined to the Tamery application distributed by wannabespace. Affected releases start with version 0.26.1 and continue through before 0.99.0. Any installation of the said range of releases that enables the cloud sync API endpoint is susceptible; newer releases beyond 0.99.0 are not yet documented as affected.

Risk and Exploitability

The CVSS score of 5.3 classifies the issue as medium severity. The EPSS score is not available, so the likelihood of exploitation cannot be quantified, but the vulnerability requires an authenticated Pro user, which may limit the attacker pool. The advisory does not list this issue under CISA’s KEV catalog, implying no known widespread exploit at the time of analysis. The attacker’s path is inferred to be an internal API call to chatsMessages.update, meaning that a credential‑compromised or legitimate Pro account with knowledge of another user’s chatId can exploit the weakness. No public exploit code is reported, but the issue is actionable by upgrading or mitigating API access.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Tamery to version 0.99.0 or later where the chatsMessages.update handler validates the chatId against the authenticated user’s permissions
  • If an upgrade is not yet possible, restrict or block the chatsMessages.update API from clients that are not authenticated as the target chat owner
  • Implement additional server‑side checks that enforce ownership of the chatId before applying message updates

Generated by OpenCVE AI on October 30, 2026 at 15:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Wannabespace
Wannabespace tamery
Vendors & Products Wannabespace
Wannabespace tamery
Type Values Removed Values Added
Description 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.
Title Tamery (Conar) 0.26.1 before 0.99.0 Authorization Bypass via chatsMessages.update
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}

cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 5, 2026, 9:34 PM
Reserved
Oct 30, 2026, 1:43 PM
Status
Deferred
Published
Oct 30, 2026, 3:16 PM
Modified
Nov 5, 2026, 10:17 PM