CVE-2026-119800: medium-severity vulnerability in IgnisDa ryot
Ryot: Cross-tenant collection read via `collectionContents`
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.3epss 0.2%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Affected products
IgnisDa · ryotRelated CVEs — IgnisDa ryot
In the same product, most dangerous first.
CVE-2026-127087LOWRyot before 10.5.6 Authorization Bypass via revokeAccessLink GraphQL MutationEPSS 0.4%CVE-2026-127085MEDIUMRyot before 10.5.6 Authorization Bypass via deployRemoveEntitiesFromCollectionJobEPSS 0.4%CVE-2026-77442MEDIUMRyot: `createOrUpdateUserIntegration` trusts a client-supplied `integrationId` with no ownership check, letting any user hijack/overwrite another user's integration (cross-tenant IDOR)EPSS 0.3%CVE-2026-127086MEDIUMRyot before 10.5.6 Authorization Bypass via createOrUpdateCollection updateIdEPSS 0.3%