# CVE-2026-108865: AmoyLab Unla through 0.10.0 OAuth2 Authentication Bypass via /authorize

> Unauthenticated attackers can bypass OAuth2 authentication to obtain valid access tokens and access protected APIs and credentials.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/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:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-pfxh-9349-4f24

## What is CVE-2026-108865?

CVE-2026-108865 is a high-severity authentication bypass vulnerability in AmoyLab Unla, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AmoyLab Unla through 0.10.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to obtain valid access tokens because the OAuth2 server never authenticates a resource owner. Attackers can register a client, request a code from /authorize, and exchange it at /token to access OAuth2-protected MCP prefixes, proxied upstream APIs and injected credentials.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-108865 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108865 is a high-severity authentication bypass vulnerability in AmoyLab Unla, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108865 in the wild and no public exploit code.

Affected product: AmoyLab Unla. 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-108865/ (Markdown: https://insights.sbomify.com/CVE-2026-108865/index.md)
```

## Sources

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

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