# CVE-2026-127087: Ryot before 10.5.6 Authorization Bypass via revokeAccessLink GraphQL Mutation


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-9cwp-c4f6-rh6m, GHSA-qgc8-wm6f-pf7h

## What is CVE-2026-127087?

CVE-2026-127087 is a low-severity vulnerability in IgnisDa ryot, published on 13 Nov 2026. 

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-127087?

1 open source package ship an affected version, including ignisda/ryot.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `ignisda/ryot` | GitHub | `pkg:github/ignisda/ryot` | All versions | 10.5.6 |

## How do I fix CVE-2026-127087?

Upgrade ignisda/ryot to 10.5.6 or later.

## Is CVE-2026-127087 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-127087 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127087 and fix it if it is affected.

What it is: CVE-2026-127087 is a low-severity vulnerability in IgnisDa ryot, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-127087 exists.

Affected packages and fixed versions:
- ignisda/ryot (GitHub): affected all versions; fixed in 10.5.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-127087/ (Markdown: https://insights.sbomify.com/CVE-2026-127087/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127087
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-127087
- OSV: https://osv.dev/vulnerability/CVE-2026-127087

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-127087/
Summaries are generated and may contain mistakes; the official description above is the record.
