# CVE-2026-111998: Vanus 0.8.0 through 0.9.0 Default Admin Credentials via Gateway

> Unauthenticated attackers can use hardcoded admin tokens to gain full cluster-admin access, manage resources, and read or publish events in Vanus.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-7rhh-2jm2-9fgj

## What is CVE-2026-111998?

CVE-2026-111998 is a critical vulnerability in vanus-labs vanus, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vanus 0.8.0 through 0.9.0 contains a default credentials vulnerability that allows unauthenticated remote attackers to gain cluster-admin access by using the hardcoded admin token. Attackers can send the fixed Bearer token to the gateway gRPC proxy port to manage namespaces, eventbuses, users, tokens, and role bindings, and read or publish events.

Weakness: CWE-1392 (Use of Default Credentials)

## Which versions are affected by CVE-2026-111998?


## How do I fix CVE-2026-111998?

No fix has been published for CVE-2026-111998 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111998 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111998 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111998 and fix it if it is affected.

What it is: CVE-2026-111998 is a critical vulnerability in vanus-labs vanus, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111998 exists.

Affected product: vanus-labs vanus. 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-111998/ (Markdown: https://insights.sbomify.com/CVE-2026-111998/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111998
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111998
- OSV: https://osv.dev/vulnerability/CVE-2026-111998

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111998/
Summaries are generated and may contain mistakes; the official description above is the record.