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-111999 Overview
CVE-2026-111999 is a missing authentication vulnerability [CWE-306] in Vanus versions 0.8.0 through 0.9.0. The flaw resides in the gateway CloudEvents HTTP receiver. Unauthenticated remote attackers can publish forged CloudEvents to any eventbus by targeting the /namespaces/{ns}/eventbus/{name}/events endpoint or the legacy /gateway/{name} path. The gateway fails to enforce token authentication and bypasses authPublish checks before accepting events. Published events are stored and delivered to downstream subscription sinks, enabling event injection into trusted event-driven workflows.
Critical Impact
Any network-reachable attacker can inject arbitrary CloudEvents into any eventbus, poisoning downstream consumers that trust gateway-delivered events.
Affected Products
- Vanus 0.8.0
- Vanus 0.9.0
- All intermediate releases between 0.8.0 and 0.9.0
Discovery Timeline
- 2026-10-18 - CVE-2026-111999 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-111999
Vulnerability Analysis
Vanus is an open-source event streaming platform that uses CloudEvents as its native event format. The gateway component exposes HTTP endpoints for publishing events to named eventbuses. In versions 0.8.0 through 0.9.0, the HTTP receiver in internal/gateway/gateway.go accepts inbound CloudEvents without validating the bearer token or evaluating the authPublish authorization hook configured for the target eventbus.
Attackers reach the receiver over the network and submit CloudEvents payloads that the gateway accepts as authentic. The gateway forwards accepted events to the controller for persistence. Subscribers configured against the targeted eventbus then receive the attacker-controlled payloads at their registered sink URLs. This turns Vanus into a vector for injecting malicious data into webhooks, serverless functions, and other downstream consumers.
Root Cause
The root cause is missing enforcement of authentication and authorization in the publish code path. The gateway handler should validate the request token and invoke the authPublish check against the target eventbus. In the affected releases, both controls are absent for the HTTP receiver routes, so any request that is syntactically valid CloudEvents is accepted. Review of the gateway source at the referenced lines confirms the publish path proceeds directly to event forwarding without an auth gate.
Attack Vector
Exploitation requires only network access to the gateway port. An attacker crafts an HTTP POST request to /namespaces/{ns}/eventbus/{name}/events or the legacy /gateway/{name} route, sets CloudEvents headers (ce-id, ce-source, ce-type, ce-specversion), and supplies a JSON body. No token, API key, or prior session is required. Successful requests return a success status and the event enters the eventbus. For technical specifics, see the GitHub Gateway Code Review, GitHub Issue #647 Discussion, and the VulnCheck Security Advisory.
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-111999
Indicators of Compromise
- Unexpected HTTP POST requests to /namespaces/*/eventbus/*/events or /gateway/* paths from unauthenticated or unfamiliar source addresses.
- CloudEvents with ce-source values that do not match any legitimate publisher in the environment.
- Spikes in event volume on eventbuses that normally receive low or steady traffic.
- Subscription sinks receiving malformed or unexpected payloads traceable to gateway-published events.
Detection Strategies
- Enable gateway access logging and alert on POST requests to publish paths that arrive without an Authorization header.
- Correlate CloudEvents ce-id and ce-source fields against an allowlist of expected publishers.
- Baseline normal event rates per eventbus and alert on statistical deviations.
Monitoring Recommendations
- Forward Vanus gateway logs to a centralized logging platform for retention and query.
- Monitor downstream sink error rates, which may surge when attacker-controlled events trigger consumer failures.
- Track network connections to the Vanus gateway port from sources outside the expected publisher set.
How to Mitigate CVE-2026-111999
Immediate Actions Required
- Restrict network reachability to the Vanus gateway port using firewall rules or Kubernetes NetworkPolicies, limiting access to known publisher workloads.
- Place the gateway behind an authenticating reverse proxy that enforces token validation before forwarding requests.
- Audit subscription sinks for evidence of attacker-injected events and purge or quarantine suspicious messages.
Patch Information
No fixed release is identified in the referenced advisory data. Monitor the GitHub Issue #647 Discussion and the VulnCheck Security Advisory for patch availability. Upgrade to a maintained release once the vendor publishes a version that enforces authentication and authPublish checks on the gateway publish path.
Workarounds
- Terminate the gateway endpoint on an ingress or API gateway that requires mutual TLS or bearer tokens for all publish requests.
- Deploy the Vanus gateway on an isolated internal network segment with no exposure to untrusted networks.
- Disable the legacy /gateway/{name} route at the proxy layer if it is not required by current publishers.
# Example NetworkPolicy restricting gateway ingress to known publisher namespace
# Apply to the namespace running Vanus
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: vanus-gateway-restrict
spec:
podSelector:
matchLabels:
app: vanus-gateway
policyTypes:
- Ingress
ingress:
- from:
- namespaceSelector:
matchLabels:
role: trusted-publishers
ports:
- protocol: TCP
port: 8080
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

