Skip to main content
VulnerabilityPublished

CVE-2026-127085: IgnisDa ryot · Insecure Direct Object Reference

Affects IgnisDa ryotSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 10.5.6 when convenient.

Data as of 13 Nov 2026, 10:03 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.3
CNA (VulnCheck)CVSS 3.14.3
Patch
Available – fixed in 10.5.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade IgnisDa ryot to 10.5.6.

Affected software

ProductAffectedFixed in
IgnisDaryotAffected
  • <10.5.6
Fixed in
  • 10.5.6
GitHubryotpkg:github/ryotOther threatsAffected
  • <10.5.6
Fixed in
  • 10.5.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade IgnisDa ryot to version 10.5.6 or later, where this authorization bypass vulnerability is fixed.

Description

IgnisDa ryot versions prior to 10.5.6 contain an authorization bypass vulnerability that allows authenticated users to delete entries from other users' collections by manipulating collectionName and creatorUserId parameters. This flaw enables attackers to target fixed collection names such as Watchlist and remove collection_to_entity rows belonging to other users. The vulnerability is fixed in version 10.5.6.

References

Community reviews

Loading reviews…