CVE-2026-119664: wannabespace tamery

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

CVSS 5.3 MediumEPSS 0.0029 · 22nd percentile

Published by the CVE Program (CNA: VulnCheck) at 30 Oct 2026, 14:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

Affected products, as the CNA wrote them
Vendor	Product	Versions
wannabespace	tamery	affected 0.26.1 to before 0.99.0 semver Other versions: unaffected

Identifiers

CVE-2026-119664

CNA

VulnCheck

Weakness (CWE)

CWE-639

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
5.3	Medium	4.0	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	CNA (VulnCheck)Used for this record
4.3	Medium	3.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N	CNA (VulnCheck)

CISA KEV Not listed.
EPSS 0.0029, the 22nd percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

30 Oct 2026, 14:16 UTC Confirmed by the CVE List
30 Oct 2026, 15:16 UTC Confirmed by NVD

Sources

References from the CNA

github.com/wannabespace/tamery/issues/601 issue-tracking
github.com/wannabespace/tamery/commit/76e75a9569f31405751a63048bae076f500c1c2c patch
github.com/wannabespace/tamery/blob/v0.32.0/apps/api/orpc/routers/chats-messages/update.ts#L9-L36 technical-description
hackmd.io/@hieuPenguinnn/conar-broken-ownership-cross-user-write third-party-advisory
github.com/wannabespace/tamery product
www.vulncheck.com/advisories/tamery-conar-0.26.1-before-0.99.0-authorization-bypass-via-chatsmessages-update third-party-advisory

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.