CVE-2026-81027

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
8.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.5Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists songquanpeng one-api versions up to and including 0.6.10 as affected. No release containing a fix is confirmed on record.

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.5HIGHmedium confidence
EG Risk
54
EG Risk 54/100

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 (value × EchelonGraph’s weight)
Severity85% × 45%
The EG Score, 8.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Aug 26, 2026
No fix on record yet.
Web page

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
Web page

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
Web page

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
Web page

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 / 106× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 183 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 84 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-13 06:23 UTCEG score recompute
  3. 2026-10-13 06:23 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-10-12 14:57 UTCEG score recompute
  6. 2026-10-11 19:21 UTCEG score recompute
  7. 2026-10-11 16:37 UTCEG score recompute
  8. 2026-10-11 13:55 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  11. 2026-10-10 06:06 UTCEG score recompute
  12. 2026-10-10 06:06 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-10-09 03:22 UTCEG score recompute
  15. 2026-10-09 03:22 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-10-08 01:51 UTCEG score recompute
  18. 2026-10-08 01:51 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-10-07 06:03 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  21. 2026-10-06 18:49 UTCEG score recompute
  22. 2026-10-06 18:49 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-10-06 07:35 UTCEG score recompute
  25. 2026-10-06 07:35 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
Show 74 more
  1. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-10-05 16:54 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  3. 2026-10-05 03:45 UTCEG score recompute
  4. 2026-10-05 03:45 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  5. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-04 15:34 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  7. 2026-10-04 04:05 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  8. 2026-10-03 16:51 UTCEG score recompute
  9. 2026-10-03 16:51 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  10. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-10-03 05:37 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  12. 2026-10-02 18:23 UTCEG score recompute
  13. 2026-10-02 18:23 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  14. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-02 07:09 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  16. 2026-10-01 19:55 UTCEG score recompute
  17. 2026-10-01 19:55 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-10-01 07:11 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  20. 2026-09-30 19:58 UTCEG score recompute
  21. 2026-09-30 19:58 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  22. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-09-30 06:03 UTCEG score recompute
  24. 2026-09-30 06:03 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  25. 2026-09-29 08:33 UTCEG score recompute
  26. 2026-09-29 08:33 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  27. 2026-09-28 21:20 UTCEG score recompute
  28. 2026-09-28 21:20 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  29. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  30. 2026-09-28 06:16 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  31. 2026-09-27 19:02 UTCEG score recompute
  32. 2026-09-27 19:02 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  33. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  34. 2026-09-27 07:49 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  35. 2026-09-26 20:35 UTCEG score recompute
  36. 2026-09-26 20:35 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  38. 2026-09-25 08:28 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  39. 2026-09-24 21:14 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  40. 2026-09-24 16:14 UTCEG score recompute
  41. 2026-09-24 16:14 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  42. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  43. 2026-09-24 05:00 UTCEG score recompute
  44. 2026-09-24 05:00 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  45. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  46. 2026-09-23 17:46 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  47. 2026-09-23 05:59 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  48. 2026-09-22 18:44 UTCEG score recompute
  49. 2026-09-22 18:44 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  50. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  51. 2026-09-22 07:23 UTCEG score recompute
  52. 2026-09-22 07:23 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  53. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  54. 2026-09-21 20:08 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  55. 2026-09-21 08:54 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  56. 2026-09-20 21:26 UTCEG score recompute
  57. 2026-09-20 21:26 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  58. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  59. 2026-09-20 10:12 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  60. 2026-09-19 22:58 UTCEG score recompute
  61. 2026-09-19 22:58 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  62. 2026-09-19 11:44 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  63. 2026-09-19 00:14 UTCEG score recompute
  64. 2026-09-19 00:14 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  65. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  66. 2026-09-18 13:01 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  67. 2026-09-18 01:47 UTCEG score recompute
  68. 2026-09-18 01:47 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  69. 2026-09-17 14:33 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  70. 2026-09-17 03:13 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  71. 2026-09-16 15:51 UTCEG score recompute
  72. 2026-09-16 15:51 UTCGHSA enrichmentGHSA-877p-7prq-ffj6 · GitHub severity HIGH · GitHub CVSS 8.5
  73. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  74. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 21st percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81027?
CVE-2026-81027 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-81027 was made public on August 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-81027 actively exploited?
CVE-2026-81027 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81027?
CVE-2026-81027 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81027?
No fix for CVE-2026-81027 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists songquanpeng one-api versions up to and including 0.6.10 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-81027 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs