AxonHub through 1.0.0-beta11 Privilege Escalation via Service Account API Key Scopes
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
AxonHub (through version 1.0.0-beta11) is affected by a privilege escalation flaw in which project users can create service account API keys with system-level permissions that are never checked. This lets an attacker with basic key-creation rights read sensitive configuration data for every channel, including base URLs and model lists.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- looplj AxonHub
through 1.0.0-beta11