# CVE-2026-108718: Rill 0.77.0 through 0.90.5 OAuth Missing Authorization via Dynamic Client Registration

> Attackers can obtain long-lived API tokens with full user permissions by exploiting missing authorization in dynamic client registration.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-r44j-vvw7-323g

## What is CVE-2026-108718?

CVE-2026-108718 is a high-severity missing authorization vulnerability in rill, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Rill 0.77.0 through 0.90.5 contains a missing authorization vulnerability in the admin OAuth server that issues authorization codes to dynamically registered clients without user consent. Attackers can register a client with the long_lived_access_token scope and lure a user to an authorization link, obtaining a non-expiring API token with the user's full permissions.

Weakness: CWE-862 (Missing Authorization)

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


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

No fix has been published for CVE-2026-108718 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108718 being exploited?

There is no known exploitation of CVE-2026-108718 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108718 is a high-severity missing authorization vulnerability in rill, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-108718 in the wild and no public exploit code.

Affected product: rill. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-108718/ (Markdown: https://insights.sbomify.com/CVE-2026-108718/index.md)
```

## Sources

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

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