---
id: "CVE-2026-119599"
kind: "vulnerability"
aliases: ["CVE-2026-119599"]
title: "AxonHub: project users can mint system-level API keys and read channel configs"
severity: "medium"
cvss: 5.3
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: [{"name": "AxonHub", "fixed": [], "affected": "<= 1.0.0-beta11", "ecosystem": "github"}]
ecosystems: []
tags: ["ai-tooling", "axonhub", "llm-gateway", "multi-tenant", "privilege-escalation", "self-hosted"]
not_affected_if: ["admin-only-key-creation", "no-project-users", "no-service-account-keys", "single-user"]
published_at: "2026-10-30T14:16:48+00:00"
first_seen_at: "2026-10-30T14:30:54+00:00"
updated_at: "2026-10-30T14:34:49+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119599", "first_seen_at": "2026-10-30T14:30:54+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-30T14:34:49+00:00"}]
---

# AxonHub: project users can mint system-level API keys and read channel configs

AxonHub through 1.0.0-beta11 does not check that the scopes on a service_account API key are ones the creator holds. A project user with write_api_keys can mint a key with system-level read_channels and use it on /admin/graphql to read every channel's configuration across all projects.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- github:AxonHub affected <= 1.0.0-beta11 fixed ?

## How to check

- Run AxonHub <= 1.0.0-beta11 (check the version in the admin UI or your image tag)? You are affected.
- List users/roles with project-level write_api_keys who lack system read_channels.
- Audit existing service_account API keys for system-level scopes (read_channels, write_channels) created by project users.

## Fix

No fixed release confirmed. Upstream fix is commit e5c904efbdabd80d74827dfae478330339c5a514 (PR #2741) per VulnCheck; run a build containing it or the first release after v1.0.0-beta11 once published. Until then, limit who holds write_api_keys.

## Timeline

- 2026-10-30T14:30:54+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119599
- 2026-10-30T14:34:49+00:00 analyst — Root cause confirmed from reporter write-up (CreateAPIKey/UpdateAPIKey skip CanGrantScopes for service_account keys; api_key.go L338/L446). VulnCheck cites fix commit e5c904e / PR #2741 on looplj/axonhub, but I could not read the PR/commit (pages empty) and releases page shows no release after v1.0.0-beta11 (2026-10-08), so no fixed release is confirmed. Not exploited; PoC steps are in the write-up (marked illustrative, not run). Nothing verified: no maintainer advisory read.

## Documents

- [advisory] VulnCheck: AxonHub through 1.0.0-beta11 Privilege Escalation via Service Account API Key Scopes https://www.vulncheck.com/advisories/axonhub-through-1.0.0-beta11-privilege-escalation-via-service-account-api-key-scopes
- [mentions] looplj/axonhub releases (latest seen: v1.0.0-beta11, 2026-10-08) https://github.com/looplj/axonhub/releases
- [poc] AxonHub privilege escalation: service_account API keys minted with scopes the creator does not hold (reporter write-up) https://hackmd.io/@hieuPenguinnn/axonhub-apikey-scope-grant-privilege-escalation

## From the sources

AxonHub through 1.0.0-beta11 contains a privilege escalation vulnerability that allows project users to assign system-level scopes by creating service_account API keys with unvalidated scopes. Attackers holding write_api_keys can mint keys with read_channels and query /admin/graphql to read every channel's configuration, including base URLs and model lists.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_