CVE-2026-81027

HIGHPre-NVD 8.58.5
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity85% × 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, 2026
No patch confirmed yet.
generic

one-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-pinning
generic

one-api/middleware/auth.go at v0.6.10 · songquanpeng/one-api · GitHub

https://github.com/songquanpeng/one-api/blob/v0.6.10/middleware/auth.go
generic

Broken 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/2410
generic

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-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-api

Vendor 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.

  1. 2026-08-30 02:38 UTCEG score recompute
  2. 2026-08-30 02:38 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 15:24 UTCGHSA enrichment
  5. 2026-08-29 04:09 UTCEG score recompute
  6. 2026-08-29 04:09 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 16:51 UTCGHSA enrichment
  9. 2026-08-28 05:32 UTCGHSA enrichment
  10. 2026-08-27 18:04 UTCEG score recompute
  11. 2026-08-27 18:04 UTCGHSA enrichment
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-27 05:39 UTCEG score recompute
  14. 2026-08-27 05:38 UTCGHSA enrichment
  15. 2026-08-26 18:23 UTCEG score recompute
  16. 2026-08-26 18:04 UTCEG score recompute
  17. 2026-08-26 16:37 UTCEG score recompute
  18. 2026-08-26 15:55 UTCEG score recompute
  19. 2026-08-26 15:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81027?
CVE-2026-81027 is a high vulnerability published on August 26, 2026. 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…
When was CVE-2026-81027 disclosed?
CVE-2026-81027 was first published in the National Vulnerability Database on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81027 actively exploited?
CVE-2026-81027 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.4% of all scored CVEs.
What is the CVSS score of CVE-2026-81027?
CVE-2026-81027 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-81027?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81027, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81027

Explore →

Is Your Infrastructure Affected by CVE-2026-81027?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.