# CVE-2026-111999: Vanus 0.8.0 through 0.9.0 Missing Authentication via Gateway CloudEvents HTTP Receiver

> Unauthenticated attackers can publish forged events to any eventbus via the gateway, bypassing authentication checks and delivering data to subscribers.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/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:** 20 Oct 2026
- **Also known as:** GHSA-v6f2-wm97-3p2m

## What is CVE-2026-111999?

CVE-2026-111999 is a high-severity missing authorization 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 missing authentication vulnerability that allows unauthenticated remote attackers to publish events to any eventbus through the gateway CloudEvents HTTP receiver. Attackers can send forged CloudEvents to the /namespaces/{ns}/eventbus/{name}/events or legacy /gateway/{name} paths, bypassing token authentication and authPublish checks, so they are stored and delivered to subscription sinks.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-111999 being exploited?

There is no known exploitation of CVE-2026-111999 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111999 is a high-severity missing authorization 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: There is no known exploitation of CVE-2026-111999 in the wild and no public exploit code.

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-111999/ (Markdown: https://insights.sbomify.com/CVE-2026-111999/index.md)
```

## Sources

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

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