Approved changes feed: RSS · Atom

cpe:2.3:a:ignisda:ryot:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorIgnisda (b95a9c66-0fda-5741-8645-b0f1b2f8b287)
ProductRyot (69c6e131-46e8-5f82-8bdf-0de513a855b1)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-127085 vulnerable 2026-11-19 05:29:47.711892 Ryot before 10.5.6 Authorization Bypass via deployRemoveEntitiesFromCollectionJob
MEDIUM (4.3)
Ryot before 10.5.6 contains an authorization bypass vulnerability that allows authenticated users to remove entries from other users' collections by supplying arbitrary collectionName and creatorUserId values. Attackers can obtain user ids from the usersList query and target fixed collection names like Watchlist to delete collection_to_entity rows belonging to other users.
Published: 2026-11-13T09:34:18.133Z
Updated: 2026-11-13T18:18:42.440Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-127086 vulnerable 2026-11-19 05:29:47.554009 Ryot before 10.5.6 Authorization Bypass via createOrUpdateCollection updateId
MEDIUM (6.3)
Ryot before 10.5.6 contains an authorization bypass vulnerability that allows authenticated users to take over other users' collections by supplying an updateId to the createOrUpdateCollection GraphQL mutation. Attackers who know a collection id can trigger ownership reassignment without checks, read its items, rewrite metadata, and evict the original owner and collaborators.
Published: 2026-11-13T09:34:17.416Z
Updated: 2026-11-18T03:43:17.969Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-127087 vulnerable 2026-11-19 05:29:47.499167 Ryot before 10.5.6 Authorization Bypass via revokeAccessLink GraphQL Mutation
LOW (3.1)
Ryot before 10.5.6 contains an authorization bypass vulnerability that allows authenticated users to revoke other users' access links by supplying an arbitrary accessLinkId. Attackers can obtain access link ids from public share URLs and revoke them without ownership checks, breaking shared access for all link users.
Published: 2026-11-13T09:34:16.780Z
Updated: 2026-11-17T13:39:48.859Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-119800 vulnerable 2026-11-19 05:28:54.069356 Ryot: Cross-tenant collection read via `collectionContents`
MEDIUM (4.3)
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-06T21:29:32.910Z
Updated: 2026-11-09T22:42:32.872Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-77442 vulnerable 2026-11-19 05:27:17.447704 Ryot: `createOrUpdateUserIntegration` trusts a client-supplied `integrationId` with no ownership check, letting any user hijack/overwrite another user's integration (cross-tenant IDOR)
MEDIUM (5.9)
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.
Published: 2026-11-06T21:26:52.401Z
Updated: 2026-11-09T13:29:06.702Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.