CVE-2026-119599 AxonHub through 1.0.0-beta11 Privilege Escalation via Service Account API Key Scopes
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-119599 and fix it if it is affected.
What it is: CVE-2026-119599 is a medium-severity vulnerability in looplj AxonHub, published on 30 Oct 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119599 exists.
Affected product: looplj AxonHub. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-119599/ (Markdown: https://insights.sbomify.com/CVE-2026-119599/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-119599?
CVE-2026-119599 is a medium-severity vulnerability in looplj AxonHub, published on 30 Oct 2026.
Official 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.
Weakness: CWE-266
Which versions are affected by CVE-2026-119599?
How do I fix CVE-2026-119599?
No fix has been published for CVE-2026-119599 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-119599 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119599 exists.
Sources
Also known as GHSA-cvgf-hhh8-56v5.