CVE-2026-81027 one-api through 0.6.10 Missing Authorization on URL-Parameter Channel Pinning

High 8.4 Published Updated

Low-privilege users can bypass authorization to access unauthorized API channels and provider keys via URL parameters.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-81027?

CVE-2026-81027 is a high-severity missing authorization vulnerability in songquanpeng one-api, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

one-api gates one of its two channel-pinning paths and not the other. middleware/auth.go permits a request to name a specific channel either through a suffix on the API key or through a URL path parameter. The suffix path is reached only after model.IsAdmin succeeds and otherwise rejects the caller, while the path-parameter branch sets the selected-channel value from c.Param("channelid") with no role check at all. The route carrying that parameter sits behind token authentication only, so any account holding a valid API token reaches it. The value flows to the distributor, which loads the channel by integer identifier with no scoping to the caller's user or group, and then sets the outbound Authorization header to that channel's stored key and directs the request at the channel's base URL. A low-privilege account can therefore pin any channel by incrementing an identifier, causing the server to make upstream requests bearing an operator-configured provider key the account was never granted, and bypassing both the per-group restriction and the channel's model allowlist.

Weakness: CWE-862

Which versions are affected by CVE-2026-81027?

How do I fix CVE-2026-81027?

No fix has been published for CVE-2026-81027 yet. Limit exposure of the affected software until one is available.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-81027 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81027 exists.

Sources

Also known as GHSA-877p-7prq-ffj6.

Is CVE-2026-81027 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free