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.
Published: 2026-11-06
Score: 4.3 Medium
EPSS: n/a
KEV: No
Impact: Data Exposure
Action: Patch Now
AI Analysis

Impact

The Ryot application contains a GraphQL query that returns an entire collection when supplied with a collection ID but does not verify that the authenticated user owns, collaborates on, or is authorized to view the collection. This results in unauthorized disclosure of the collection owner’s identity, collection name, description, reviews, and all items, allowing a user to read data from other tenants. The weakness is a CWE‑639 third‑party access flaw and does not allow code execution or privilege escalation, but it does enable cross‑tenant data leakage.

Affected Systems

All versions of the IgnisDa Ryot self‑hosted personal tracking application prior to v10.5.6 are affected. The vulnerability is fixed in release v10.5.6 and any newer versions.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate severity. No EPSS score is available and the vulnerability is not listed in the CISA KEV catalog, suggesting a lower likelihood of widespread exploitation at this time. The attack requires an authenticated user who knows or can guess a valid collection ID; it is therefore exploitable in environments where collection IDs are exposed or enumerated. Even though the risk is moderate, the potential for sensitive data leakage across tenant boundaries warrants timely remediation.

Generated by OpenCVE AI on November 6, 2026 at 22:51 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Ryot to version 10.5.6 or later, which includes permission checks for the collectionContents query.
  • Implement role‑based access control for the collectionContents GraphQL query to ensure only owners or collaborators can retrieve collection data, addressing the CWE‑639 weakness.
  • If a patch cannot be applied immediately, restrict GraphQL endpoint usage to administrators or explicitly authorized users and prevent collection ID enumeration to limit exposure.

Generated by OpenCVE AI on November 6, 2026 at 22:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 06 Nov 2026 21:45:00 +0000

Type Values Removed Values Added
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.
Title Ryot: Cross-tenant collection read via `collectionContents`
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-06T21:29:32.910Z

Reserved: 2026-10-30T16:28:37.900Z

Link: CVE-2026-119800

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-06T22:17:50.480

Modified: 2026-11-06T22:17:50.480

Link: CVE-2026-119800

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-06T23:00:11Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key