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.
CVE-2026-81027
Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. a secondary CVSS source baseline 8.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.5
- EG Score
- 8.5(high)
- EG Risk
- 54(Track)EG Risk 54/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity85% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 26, 2026
Advisory Details (4)
Auto-updated Aug 26, 2026one-api through 0.6.10 Missing Authorization on URL-Parameter Channel Pinning | Advisories | VulnCheck
https://www.vulncheck.com/advisories/one-api-through-0.6.10-missing-authorization-on-url-parameter-channel-pinningone-api/middleware/auth.go at v0.6.10 · songquanpeng/one-api · GitHub
https://github.com/songquanpeng/one-api/blob/v0.6.10/middleware/auth.goBroken access control / cross-tenant channel theft via the oneapi/proxy channelid URL param (admin gate missing on one of two channel-pinning paths) · Issue #2410 · songquanpeng/one-api · GitHub
https://github.com/songquanpeng/one-api/issues/2410GitHub - songquanpeng/one-api: LLM API 管理 & 分发系统,支持 OpenAI、Azure、Anthropic Claude、Google Gemini、DeepSeek、字节豆包、ChatGLM、文心一言、讯飞星火、通义千问、360 智脑、腾讯混元等主流模型,统一 API 适配,可用于 key 管理与二次分发。单可执行文件,提供 Docker 镜像,一键部署,开箱即用。LLM API management & key redistribution system, unifying multiple providers under a single API. Single binary, Docker-read...
GitHub - songquanpeng/one-api: LLM API 管理 & 分发系统,支持 OpenAI、Azure、Anthropic Claude、Google Gemini、DeepSeek、字节豆包、ChatGLM、文心一言、讯飞星火、通义千问、360 智脑、腾讯混元等主流模型,统一 API 适配,可用于 key 管理与二次分发。单可执行文件,提供 Docker 镜像,一键部署,开箱即用。LLM API management & key redistribution system, unifying multiple providers under a single API. Single binary, Docker-ready, with an English UI. · GitHub
https://github.com/songquanpeng/one-apiVendor Advisories for CVE-2026-81027(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 02:38 UTCEG score recompute
- 2026-08-30 02:38 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 15:24 UTCGHSA enrichment
- 2026-08-29 04:09 UTCEG score recompute
- 2026-08-29 04:09 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 16:51 UTCGHSA enrichment
- 2026-08-28 05:32 UTCGHSA enrichment
- 2026-08-27 18:04 UTCEG score recompute
- 2026-08-27 18:04 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 05:39 UTCEG score recompute
- 2026-08-27 05:38 UTCGHSA enrichment
- 2026-08-26 18:23 UTCEG score recompute
- 2026-08-26 18:04 UTCEG score recompute
- 2026-08-26 16:37 UTCEG score recompute
- 2026-08-26 15:55 UTCEG score recompute
- 2026-08-26 15:54 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-81027?
When was CVE-2026-81027 disclosed?
Is CVE-2026-81027 actively exploited?
What is the CVSS score of CVE-2026-81027?
How do I remediate CVE-2026-81027?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81027
Is Your Infrastructure Affected by CVE-2026-81027?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.