CVE-2026-108865

AmoyLab Unla through 0.10.0 OAuth2 Authentication Bypass via /authorize

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

Analysis

AI-generated

Technical impact

The vulnerability resides in the OAuth2 server component of AmoyLab Unla, which never authenticates the resource owner before generating an authorization code. As a result, a malicious actor can register a client, request a code through the /authorize endpoint, and exchange that code at /token to receive a functional access token. Possession of this token allows unrestricted access to all OAuth2‑protected services exposed by Unla, including any MCP prefixes, proxied upstream APIs, and injected credential endpoints, effectively granting the attacker the same privileges as a legitimate user.

Affected Systems

AmoyLab Unla versions up to and including 0.10.0 contain this flaw. All deployments that have not applied a fix or updated the application to a later release are vulnerable.

Risk and Exploitability

The CVSS score of 8.8 categorizes this issue as high severity. Although EPSS data is unavailable and the vulnerability is not listed in KEV, the attack does not require privileged network access; it can be carried out by any host that can reach the /authorize and /token endpoints over HTTP. Consequently, the risk of exploitation remains significant for exposed instances.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest AmoyLab Unla release that validates the resource owner before issuing an authorization code.
  • If an update cannot be deployed immediately, restrict external traffic to the /authorize and /token endpoints via firewall rules or IP whitelisting, and consider enabling mutual TLS if available.
  • Reconfigure or disable any self‑issued token registration mechanism in Unla so that only authenticated resource owners can obtain authorization codes, ensuring that user authentication is mandatory before code issuance.

Generated by OpenCVE AI on October 11, 2026 at 16:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
First Time appeared Amoylab
Amoylab unla
Vendors & Products Amoylab
Amoylab unla
Type Values Removed Values Added
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.
Title AmoyLab Unla through 0.10.0 OAuth2 Authentication Bypass via /authorize
Weaknesses CWE-287
References
Metrics cvssV3_1

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

cvssV4_0

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

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 14, 2026, 4:48 PM
Reserved
Oct 11, 2026, 1:17 PM
Status
Deferred
Published
Oct 11, 2026, 2:17 PM
Modified
Oct 16, 2026, 7:18 PM