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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/looplj/axonhub/commit/e5c904efbdabd80d74827dfae478330339c5a514 patch
- https://github.com/looplj/axonhub/pull/2741 patch, issue-tracking
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.3 · loopljNVD modified 2026-10-30 14:07
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 8
- https://github.com/looplj/axonhub/commit/e5c904efbdabd80d74827dfae478330339c5a514 patch
- https://github.com/looplj/axonhub/pull/2741 patch, issue-tracking
- https://github.com/looplj/axonhub/issues/2724 issue-tracking
- https://github.com/looplj/axonhub/blob/v1.0.0-beta11/internal/server/biz/api_key.go#L340 technical-description
- https://github.com/looplj/axonhub/blob/v1.0.0-beta11/internal/server/biz/api_key.go#L448 technical-description
- https://hackmd.io/@hieuPenguinnn/axonhub-apikey-scope-grant-privilege-escalation third-party-advisory
- https://github.com/looplj/axonhub product
- https://www.vulncheck.com/advisories/axonhub-through-1.0.0-beta11-privilege-escalation-via-service-account-api-key-scopes third-party-advisory