AxonHub through 1.0.0-beta11 Privilege Escalation via Service Account API Key Scopes
Impact
AxonHub through 1.0.0-beta11 has a privilege escalation vulnerability, allowing project users with write_api_keys access to assign system-level scopes and read channel configurations. The weakness is due to unvalidated scopes in service_account API keys. This may impact users of affected versions.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
looplj · VulnCheck
AxonHub
1 range
looplj · VulnCheck
AxonHub
Package identity
pkg:golang/github.com/looplj/axonhubExplore github.com/looplj/axonhub →Identity supplied by VulnCheck. Version matching requires compatible range evidence.
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → through 1.0.0-beta11
custom versions
Other versions: unaffected
Original source description
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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-119599View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.