CVE-2026-108581

Octop through 1.0.2b6 Missing Authorization Exposes Provider API Keys via /api/providers

Published Oct 10, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

TencentCloud Octop versions up to 1.0.2b6 allow authenticated users with low privileges to read stored provider API keys by sending GET requests to /api/providers and /api/voice/providers. The endpoints only validate the presence of a JWT and fail to check the user's role, exposing plaintext keys that can be used to abuse downstream LLM and voice provider accounts. The weakness, identified as CWE-862, results in loss of confidentiality for the provider credentials and potential service disruption if the keys are misused. This flaw does not grant arbitrary code execution but enables attacker credential compromise that can be leveraged for further attacks.

Affected Systems

TencentCloud Octop, from its initial release through version 1.0.2b6. No specific build numbers beyond 1.0.2b6 are impacted, and newer releases may have fixed the issue.

Risk and Exploitability

The vulnerability has a CVSS score of 7.1, indicating moderate to high severity. Because the EPSS score is unavailable and the flaw is not listed in the CISA KEV catalog, public exploitation data is limited. Attackers can exploit the flaw by simply authenticating with a valid JWT, which most users possess, and then issuing GET requests to the exposed endpoints. No further prerequisites are required, making the attack straightforward for any authenticated user. The missing role validation provides an easy route to credential disclosure, and since the keys are stored in plaintext, the impact is immediate and significant.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Octop to a version where the authorization check is enforced.
  • Configure access controls so that only users with administrative roles can query /api/providers and /api/voice/providers.
  • Monitor API usage for anomalous request patterns and audit exposed key access.

Generated by OpenCVE AI on October 10, 2026 at 17:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Tencentcloud
Tencentcloud octop
Vendors & Products Tencentcloud
Tencentcloud octop
Type Values Removed Values Added
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.
Title Octop through 1.0.2b6 Missing Authorization Exposes Provider API Keys via /api/providers
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 7.1, 'vector': '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 18, 2026, 11:53 AM
Reserved
Oct 10, 2026, 3:51 PM
Status
Deferred
Published
Oct 10, 2026, 4:16 PM
Modified
Oct 18, 2026, 12:16 PM