The vulnerability allows a legitimate user with an API token to pin an arbitrary channel by specifying its numeric ID in the URL path. Because the route only authenticates the caller’s token and does not enforce an administrative or role check, the request can be made by any registered user. Once the channel identifier is accepted, the server loads the channel configuration directly and forwards the request to the provider using the channel’s stored key. This bypasses any per-group restrictions and the provider’s allowlist, resulting in the token holder gaining the ability to use privileged provider credentials and potentially access resources or data that should be restricted.

Vote”“songquanpeng:one-api” is the vendor and product name. The issue affects versions up through 0.6.10 of the software. No later revision that includes the fix is currently listed in the official references provided.

The CVSS score of 8.4 indicates high severity exploitation risk, and the absence of an EPSS score means no public exploitation data is available yet, but the flaw remains highly valuable for attackers who can obtain a valid API token. Because the token authentication is the sole guard, the attack vector is remote and does not require special network privileges. There is no listing in the CISA KEV catalog as of the data presented, but the nature of the flaw—privilege escalation via a missing authorization check—makes it a strong candidate for rapid exploitation once a product is deployed. The vulnerability is exploitable by any user with a valid token, which is a common condition for many deployments of this API, so the potential impact is widespread and immediate once a suitable token is acquired.