CVE-2026-81027: Missing Authorization in songquanpeng one-api
Description
CVE-2026-81027 is a high-severity authorization vulnerability in songquanpeng one-api versions up to 0.6.10. The API improperly authorizes requests that specify a channel via a URL path parameter, allowing any user with a valid API token to access channels without proper role checks. This flaw enables low-privilege accounts to impersonate higher-privilege channels by manipulating the channel identifier, bypassing group restrictions and channel allowlists.
CVSS v4.0
Score 8.4high
Affected software
songquanpeng
one-api
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because one-api gates one of its two channel-pinning paths with an admin check but not the other. Specifically, the middleware/auth.go permits channel selection either through an API key suffix or a URL path parameter. The suffix path requires admin validation, but the path-parameter branch does not enforce any role checks and is protected only by token authentication. Consequently, any valid token holder can specify arbitrary channel IDs, causing the server to forward requests with the channel's authorization key. This bypasses per-group restrictions and channel allowlists, allowing unauthorized access to channels and their associated privileges.
Potential Impact
An attacker with a valid API token but low privileges can exploit this vulnerability to access or act on behalf of any channel by incrementing the channel identifier. This leads to unauthorized use of operator-configured provider keys and bypasses intended access controls, potentially exposing sensitive data or allowing unauthorized actions within the system. The vulnerability has a CVSS 4.0 base score of 8.4, indicating high severity with network attack vector, low attack complexity, no user interaction, and significant impact on confidentiality and integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict API token issuance to trusted users only and monitor for unusual channel access patterns. Avoid using the vulnerable path-parameter channel selection mechanism if possible. Implement additional access controls or request validation to ensure channel identifiers correspond to authorized user groups.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-26T15:23:05.016Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a8f0bdbacd9273b4917dedc
Added to database: 08/26/2026, 15:52:59 UTC
Last enriched: 09/09/2026, 17:22:52 UTC
Last updated: 10/10/2026, 06:48:19 UTC
Views: 64
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.