Ryot: Cross-tenant collection read via `collectionContents`
- Exploited
- No known exploitation
- Fix
- Fixed in 10.5.6
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 10.5.6.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 7/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Ryot, a self-hosted personal tracking application, lets any logged-in user who knows another collection's ID read that collection's owner identity, name and description, reviews, and full item list. An attacker reaches this remotely over the network with an ordinary account and needs no action from the victim.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 10.5.6.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- IgnisDa ryot
fixed in 10.5.6
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119800
Is CVE-2026-119800 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-119800?
ryot: before 10.5.6.Source: cve.now feed data
How do I fix CVE-2026-119800?
Upgrade to a fixed version: 10.5.6.Source: cve.now feed data