Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112000 Overview
CVE-2026-112000 is a missing authorization vulnerability [CWE-862] affecting Vanus versions 0.8.0 through 0.9.0. The flaw resides in the gateway component, where streaming RPCs including Subscribe, Ack, and unregistered methods bypass permission checks. Any authenticated user can supply another tenant's subscription identifier to hijack it, read and acknowledge events, and starve the legitimate consumer. The same gap exposes administrative methods such as ListUser, enabling cluster-wide user enumeration across tenants.
Critical Impact
Authenticated low-privileged attackers can hijack cross-tenant subscriptions, intercept event streams, disrupt legitimate consumers, and enumerate cluster users.
Affected Products
- Vanus 0.8.0
- Vanus 0.9.0
- Vanus gateway streaming RPC interface (versions 0.8.0 through 0.9.0)
Discovery Timeline
- 2026-10-18 - CVE-2026-112000 published to the National Vulnerability Database (NVD)
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-112000
Vulnerability Analysis
Vanus is an open-source event streaming platform. The gateway terminates client gRPC connections and multiplexes them onto backend services. In versions 0.8.0 through 0.9.0, the gateway's authentication interceptor validates the caller's identity but does not enforce per-method or per-resource authorization on streaming RPCs. The result is a broken access control condition where authentication is treated as sufficient to invoke sensitive operations.
An attacker with any valid tenant credential can issue a Subscribe call referencing a subscription owned by a different tenant. The gateway proxies the call without validating ownership, so the attacker receives events destined for the legitimate consumer. The attacker can also issue Ack for those events, which starves the real consumer and prevents redelivery. Separately, unregistered administrative methods such as ListUser are reachable through the same gateway path and leak user records across the cluster.
Root Cause
The root cause is a missing authorization check in the gateway's interceptor and proxy layer. The relevant logic in internal/gateway/auth/auth.go, internal/gateway/auth/interceptor.go, and internal/gateway/proxy/proxy.go authenticates the request but does not verify that the subject owns the target subscription or holds the role required to invoke administrative RPCs. Methods that were never registered in the authorization map default to permissive behavior rather than deny.
Attack Vector
Exploitation requires network access to the Vanus gateway and valid credentials for any tenant. The attacker enumerates or guesses subscription identifiers, issues a Subscribe stream against the target identifier, and begins consuming events in parallel with or in place of the owner. Ack calls commit offsets for the hijacked subscription, denying delivery to the legitimate consumer. ListUser returns the full user set across tenants, supporting lateral reconnaissance.
No synthetic exploit code is published. Implementation details are documented in the VulnCheck Security Advisory and the referenced GitHub Auth Interceptor Code.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-112000
Indicators of Compromise
- Gateway logs showing Subscribe or Ack RPCs where the authenticated principal's tenant does not match the tenant owning the referenced subscription identifier.
- Invocations of administrative methods such as ListUser from accounts that do not hold cluster-admin roles.
- Legitimate consumers reporting missed events, stalled offsets, or unexpectedly acknowledged messages without client activity.
- Spikes in streaming RPCs from a single credential targeting multiple subscription identifiers in rapid succession.
Detection Strategies
- Enable verbose RPC logging at the Vanus gateway and alert on cross-tenant mismatches between the caller claim and the subscription owner.
- Baseline per-account subscription identifiers and flag calls that reference identifiers outside the baseline.
- Correlate consumer lag metrics with Ack sources to detect acknowledgments issued by principals that are not the registered consumer.
Monitoring Recommendations
- Forward gateway access logs and gRPC audit events into a central analytics pipeline for cross-tenant correlation.
- Monitor for invocations of unregistered or administrative RPC methods and treat them as high-severity events pending patch.
- Track user and subscription enumeration patterns across short time windows to catch reconnaissance.
How to Mitigate CVE-2026-112000
Immediate Actions Required
- Inventory all Vanus deployments and identify instances running 0.8.0 or 0.9.0 exposed to untrusted tenants or networks.
- Restrict gateway network reachability to trusted service accounts until an authorization fix is deployed.
- Rotate tenant credentials and subscription identifiers that may have been exposed to unauthorized consumers.
- Review historical gateway logs for cross-tenant Subscribe, Ack, and ListUser activity and investigate matches.
Patch Information
At publication, no vendor-fixed release is referenced in the NVD record for CVE-2026-112000. Track the upstream GitHub Issue #647 and the VulnCheck Security Advisory for a patched version. Apply the upstream fix as soon as it is published and redeploy gateway instances.
Workarounds
- Place the Vanus gateway behind an authenticating reverse proxy that enforces per-tenant method allow-lists and blocks ListUser and other administrative RPCs.
- Segment tenants onto isolated Vanus clusters so a compromised credential cannot reach foreign subscription identifiers.
- Disable or restrict unregistered RPC methods at the ingress layer using gRPC method filtering.
- Short-lived tenant tokens with scoped claims reduce the blast radius if credentials are reused for cross-tenant calls.
# Example: block administrative RPC methods at an Envoy-fronted Vanus gateway
# until an upstream fix for CVE-2026-112000 is applied
http_filters:
- name: envoy.filters.http.rbac
typed_config:
"@type": type.googleapis.com/envoy.extensions.filters.http.rbac.v3.RBAC
rules:
action: DENY
policies:
deny-admin-rpcs:
permissions:
- header:
name: ":path"
string_match:
safe_regex:
regex: "/.*(ListUser|Subscribe|Ack)$"
principals:
- any: true
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

