Read the docs

Authorization bypass in Ryot lets users remove other users' collection entries

Priority MEDIUM 57CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.

Summary

Ryot before 10.5.6 contains an authorization bypass that lets authenticated users remove entries from other users' collections. By supplying arbitrary collection names and creator user ids, an attacker can delete collection entries belonging to other users. An attacker with low privileges can do this over the network without user interaction, and it affects integrity and availability of the data. The weakness is CWE-639, authorization bypass through a user-controlled key.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00374 31st percentileScored 2026-11-16
Fix Fixed ryot (IgnisDa): 10.5.6

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
IgnisDaryotbefore 10.5.610.5.6Patch availableCNA
  • ryot VendorIgnisDa Affected before 10.5.6 Fixed in 10.5.6 Patch available CNA

Remediation

Upgrade IgnisDa ryot to version 10.5.6 or later, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA ryot (IgnisDa) Fixed in 10.5.6

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    IgnisDa ryot 10.5.6

    3 records Highest priority Priority MEDIUM 1 MEDIUM, 2 LOW

    Other records, highest priority first

    • TI-2026-91420 Ryot Authorization Bypass via createOrUpdateCollection updateIdPriority LOW 24
    • TI-2026-91421 Ryot Authorization Bypass via revokeAccessLink GraphQL MutationPriority LOW 12

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-127085
  2. 2026-11-13 Alias added: GHSA-3g3g-3r3m-hvpw
  3. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2026-86144 Ryot lets users hijack other users' integrations by integration ID CVSS 3.1MEDIUM 5.9
  • TI-2026-91420 Ryot Authorization Bypass via createOrUpdateCollection updateId CVSS 4.0MEDIUM 5.3
  • TI-2026-86149 Cross-tenant collection read via collectionContents in Ryot CVSS 3.1MEDIUM 4.3
  • TI-2026-91421 Ryot Authorization Bypass via revokeAccessLink GraphQL Mutation CVSS 4.0LOW 2.3

Sources