---
id: "CVE-2026-112000"
kind: "vulnerability"
aliases: ["CVE-2026-112000"]
title: "Vanus gateway lets any logged-in user hijack other tenants' subscriptions"
severity: "high"
cvss: 7.6
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "vanus", "fixed": [], "affected": ">= 0.8.0, <= 0.9.0", "ecosystem": "github"}]
ecosystems: []
tags: ["eventbus", "missing-authorization", "multi-tenant", "package", "self-hosted", "vanus"]
not_affected_if: ["gateway-not-exposed", "managed-hosting", "single-tenant", "versions-outside-0.8.0-0.9.0"]
published_at: "2026-10-18T12:17:12+00:00"
first_seen_at: "2026-10-23T21:57:15+00:00"
updated_at: "2026-10-25T03:44:41+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112000", "first_seen_at": "2026-10-23T21:57:15+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-25T03:44:41+00:00"}]
---

# Vanus gateway lets any logged-in user hijack other tenants' subscriptions

Vanus versions 0.8.0 through 0.9.0 let any authenticated user call Subscribe, Ack and unregistered gateway methods without permission checks. An attacker who knows another tenant's subscription ID can take over that subscription, read and acknowledge its events, starve the legitimate consumer, and list cluster users.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- github:vanus affected >= 0.8.0, <= 0.9.0 fixed ?

## How to check

Run the gateway/controller image or binary and check its version: 0.8.0 through 0.9.0 is affected (the latest release is 0.9.0, so all releases from 0.8.0 on). Also check whether the gateway gRPC port is reachable by more than one tenant or by untrusted token holders. In source, server/gateway/auth/interceptor.go has a '// todo stream authorize' stream interceptor, and auth.go returns nil for unknown methods.

## Fix

No fixed release as of 2026-10-25; latest release v0.9.0 is affected. Upstream issue #647 is open. Mitigate by not exposing the gateway to untrusted users and by moving to a single tenant.

## Timeline

- 2026-10-23T21:57:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-112000
- 2026-10-25T03:44:41+00:00 analyst — No fix exists: reporter issue vanus-labs/vanus#647 (open, 'Fixed version: none') and releases (latest v0.9.0, 2023) show no patched release; VulnCheck CNA advisory confirms 0.8.0-0.9.0. Issue 4 is from static analysis only, no PoC published. Same issue #647 covers sibling CVEs 111998 (default admin token) and 111999 (unauth publish on :8081), which make this reachable without any login. Nothing marked verified: no vendor statement.

## Documents

- [advisory] VulnCheck: Vanus 0.8.0-0.9.0 Missing Authorization in Gateway Streaming RPCs https://www.vulncheck.com/advisories/vanus-0.8.0-through-0.9.0-missing-authorization-in-gateway-streaming-rpcs
- [describes] Vanus #647 [Security] hardcoded token, unauth publish, SSRF, missing authorization (reporter) https://github.com/vanus-labs/vanus/issues/647
- [mentions] Vanus releases (latest v0.9.0, 2023-09) https://github.com/vanus-labs/vanus/releases

## From the sources

Vanus 0.8.0 through 0.9.0 contains a missing authorization vulnerability in the gateway that allows any authenticated user to call Subscribe, Ack, and unregistered methods without permission checks. Attackers can supply another tenant's subscription ID to Subscribe to hijack it, read and acknowledge its events, starve the legitimate consumer, and enumerate cluster users via ListUser.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_