# CVE-2026-108581: Octop through 1.0.2b6 Missing Authorization Exposes Provider API Keys via /api/providers

> Authenticated low-privileged users can read plaintext provider API keys via unprotected endpoints, enabling abuse of upstream accounts.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-c344-c8vm-8rxv

## What is CVE-2026-108581?

CVE-2026-108581 is a high-severity missing authorization vulnerability in TencentCloud Octop, published on 10 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TencentCloud Octop through 1.0.2b6 contains a missing authorization vulnerability that allows authenticated low-privileged users to read stored provider API keys via GET /api/providers and GET /api/voice/providers. Attackers can query these endpoints, which only validate the JWT, to obtain plaintext LLM and voice provider API keys and abuse the upstream provider accounts.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-108581 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108581 is a high-severity missing authorization vulnerability in TencentCloud Octop, published on 10 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108581 in the wild and no public exploit code.

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

## Sources

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

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