A missing authorization flaw in one-api allows low-privilege users to hijack administrative channel configurations, posing a significant risk of unauthorized resource consumption and potential data exposure.

The application fails to perform role-based access control (RBAC) on the URL parameter channel-pinning path, allowing any authenticated user to specify an arbitrary channel identifier. While administrative paths are correctly gated, the vulnerable endpoint permits users to force the application to use operator-configured provider keys that the user is not authorized to access.

Successful exploitation allows a low-privilege user to perform requests using administrative-level provider keys. This results in unauthorized resource usage, potential financial costs if the provider is metered, and the ability to bypass security policies such as per-group restrictions and model allowlists. Given the CVSS score of 8.5, this high-severity vulnerability represents a significant risk to the integrity and confidentiality of the service integration.

Immediate Action: Update one-api to a version beyond 0.6.10 where the authorization check for the channel-pinning parameter is correctly enforced.

Proactive Monitoring: Review API usage logs for unusual patterns, specifically looking for requests that target non-standard channel identifiers or unexpected increases in provider key usage.

Compensating Controls: Implement strict Web Application Firewall (WAF) rules to inspect and sanitize incoming API requests, specifically blocking requests that attempt to pass unauthorized channel identifiers via URL parameters.

Public Exploit Available: Unknown

This vulnerability presents a critical security gap that undermines the multi-tenancy and authorization model of the one-api platform. Organizations should prioritize the deployment of the vendor-supplied security patch immediately. Until the patch is applied, administrators should audit current API token usage and consider restricting access to the affected endpoints if the business use case permits.