CVE-2026-77442: medium-severity vulnerability in IgnisDa ryot
Ryot: `createOrUpdateUserIntegration` trusts a client-supplied `integrationId` with no ownership check, letting any user hijack/overwrite another user's integration (cross-tenant IDOR)
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 5.9epss 0.3%
Ryot is a self-hosted personal tracking application. Prior to 10.4.0, the createOrUpdateUserIntegration GraphQL mutation in crates/services/user/src/integration_operations.rs allows a low-privileged authenticated user to supply another user's integrationId to create_or_update_user_integration() without an ownership check. SeaORM treats the supplied primary key as an update target, and the operation assigns the caller's user_id while replacing the targeted integration's provider_specifics and other configuration, which can transfer ownership, overwrite configuration, or disable the victim's integration. Exploitation requires obtaining the victim's non-brute-forceable integration id, and the vulnerable update does not disclose existing stored credential values. This issue is fixed in version 10.4.0.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L
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-127086MEDIUMRyot before 10.5.6 Authorization Bypass via createOrUpdateCollection updateIdEPSS 0.3%CVE-2026-119800MEDIUMRyot: Cross-tenant collection read via `collectionContents`EPSS 0.2%