# CVE-2026-119800: Ryot: Cross-tenant collection read via `collectionContents`


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-pv32-9hxm-ph4v

## What is CVE-2026-119800?

CVE-2026-119800 is a medium-severity vulnerability in IgnisDa ryot, published on 6 Nov 2026. 

### Official description

Ryot is a self-hosted personal tracking application. Prior to 10.5.6, the collectionContents GraphQL query implemented by collection_contents() in crates/services/collection/src/content_operations.rs accepts a caller-controlled CollectionContentsInput.collection_id and returns a collection without checking whether the authenticated user owns it, collaborates on it, or may view it. The caller's user id is used only to annotate the response, allowing any authenticated user who obtains another collection's id to read the owner's identity, collection name and description, reviews, and complete item list across the tenant boundary. This issue is fixed in version 10.5.6.

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

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


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

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

## Is CVE-2026-119800 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119800 is a medium-severity vulnerability in IgnisDa ryot, published on 6 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119800 in the wild and no public exploit code.

Affected product: IgnisDa ryot. 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-119800/ (Markdown: https://insights.sbomify.com/CVE-2026-119800/index.md)
```

## Sources

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

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