# CVE-2026-119663: Tamery (Conar) 0.32.0 before 0.99.0 Broken Authorization via connectionsResources.create


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-mf38-vc74-jfg4

## What is CVE-2026-119663?

CVE-2026-119663 is a medium-severity vulnerability in wannabespace tamery, published on 30 Oct 2026. 

### Official description

Tamery (formerly Conar) 0.32.0 before 0.99.0 contains a broken authorization vulnerability in the cloud sync API connectionsResources.create handler that allows authenticated users to attach resources to other users' connections. Attackers owning one connection can include a victim's connectionId in a batch request to insert attacker-named resource rows listed by the victim's client.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-119663?


## How do I fix CVE-2026-119663?

No fix has been published for CVE-2026-119663 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119663 being exploited?

There is no known exploitation of CVE-2026-119663 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119663 and fix it if it is affected.

What it is: CVE-2026-119663 is a medium-severity vulnerability in wannabespace tamery, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119663 in the wild and no public exploit code.

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-119663/ (Markdown: https://insights.sbomify.com/CVE-2026-119663/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119663
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119663
- OSV: https://osv.dev/vulnerability/CVE-2026-119663

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119663/
Summaries are generated and may contain mistakes; the official description above is the record.