CVE-2026-119664 Tamery (Conar) 0.26.1 before 0.99.0 Authorization Bypass via chatsMessages.update
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-119664 and fix it if it is affected.
What it is: CVE-2026-119664 is a medium-severity vulnerability in wannabespace tamery, published on 30 Oct 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119664 exists.
Affected product: wannabespace tamery. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-119664/ (Markdown: https://insights.sbomify.com/CVE-2026-119664/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-119664?
CVE-2026-119664 is a medium-severity vulnerability in wannabespace tamery, published on 30 Oct 2026.
Official 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.
Weakness: CWE-639
Which versions are affected by CVE-2026-119664?
How do I fix CVE-2026-119664?
No fix has been published for CVE-2026-119664 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-119664 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119664 exists.
Sources
Also known as GHSA-cqj4-h3hg-hjvc.