{"description":"Trending threats, MITRE ATT\u0026CK coverage, and detection metadata. Fed continuously.","favicon":"https://feed.craftedsignal.io/favicon-32x32.png","feed_url":"https://feed.craftedsignal.io/vendors/one-api/feed.json","home_page_url":"https://feed.craftedsignal.io/","icon":"https://feed.craftedsignal.io/apple-touch-icon.png","items":[{"_cs_actors":[],"_cs_cpes":[],"_cs_cves":[{"cvss":8.5,"id":"CVE-2026-81027"}],"_cs_exploited":false,"_cs_has_poc":false,"_cs_poc_references":[],"_cs_products":["one-api"],"_cs_severities":["high"],"_cs_tags":[],"_cs_type":"advisory","_cs_vendors":["one-api"],"content_html":"\u003cp\u003eThe one-api service contains an authorization bypass vulnerability (CVE-2026-81027) within its channel-pinning logic in middleware/auth.go. The application provides two methods for specifying a channel: a suffix on the API key and a URL path parameter. While the API key suffix method properly validates the user's administrative status, the URL path-parameter branch fails to perform any role checks before processing the request.\u003c/p\u003e\n\u003cp\u003eAn attacker with a valid, low-privilege API token can manipulate the \u0026quot;channelid\u0026quot; parameter in the URL. The application then uses this identifier to load the corresponding channel's credentials without verifying if the caller is authorized to access that specific channel or group. Consequently, the server proxies requests to the upstream provider using the operator's configured keys, effectively bypassing security controls including per-group restrictions and model allowlists. This allows unauthorized access to service provider endpoints and potentially incurs costs or exposes sensitive configuration data.\u003c/p\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation allows low-privileged users to bypass access controls and interact with unauthorized upstream LLM providers or services using the organization's API keys. This can lead to unauthorized resource consumption, potential data exfiltration via third-party providers, and the circumvention of established cost-management and policy-based controls. The vulnerability affects the core authorization flow of the one-api platform.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eUpgrade one-api to the version containing the fix for CVE-2026-81027 immediately.\u003c/li\u003e\n\u003cli\u003eReview application logs for anomalous patterns in requests containing channel identifiers in the URI path.\u003c/li\u003e\n\u003cli\u003eMonitor for requests where the user context does not align with the requested channel ID or administrative roles.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-08-26T16:22:09Z","date_published":"2026-08-26T16:22:09Z","id":"https://feed.craftedsignal.io/briefs/2026-08-one-api-auth-bypass/","summary":"An authorization flaw in one-api allows authenticated users to bypass role checks and per-group restrictions by manipulating channel ID parameters to access unauthorized upstream provider keys.","title":"Authorization Bypass in one-api via Channel Pinning","url":"https://feed.craftedsignal.io/briefs/2026-08-one-api-auth-bypass/"}],"language":"en","title":"CraftedSignal Threat Feed - One-Api","version":"https://jsonfeed.org/version/1.1"}