CVE-2026-111999 vanus-labs CVE debrief

Who should care

Defenders responsible for Vanus deployments, particularly those using versions 0.8.0 through 0.9.0, should assess exposure and verify the authenticity of events published through the gateway CloudEvents HTTP receiver.

Why it matters

CVE-2026-111999 is a high-severity vulnerability in Vanus versions 0.8.0 through 0.9.0, allowing unauthenticated remote attackers to publish events to any eventbus through the gateway CloudEvents HTTP receiver. Defenders should prioritize verifying exposure and assessing the authenticity of events.

• Potential unauthorized event publication
• Possible bypass of authentication and authorization checks
• Required verification of Vanus versions and configurations
• Potential impact on eventbus and subscription sinks

Technical summary

The CVE-2026-111999 vulnerability exists in Vanus versions 0.8.0 through 0.9.0, allowing unauthenticated remote attackers to publish events to any eventbus through the gateway CloudEvents HTTP receiver. The vulnerability is caused by missing authentication, enabling attackers to bypass token authentication and authPublish checks. Defenders should prioritize verifying exposure of Vanus versions 0.8.0 through 0.9.0 and assessing the authenticity of events published through the gateway CloudEvents HTTP receiver. This requires verifying the authenticity of events and implementing authentication and authorization checks for event publication.

Defensive priority

Defenders should prioritize verifying exposure of Vanus versions 0.8.0 through 0.9.0 and assessing the authenticity of events published through the gateway CloudEvents HTTP receiver.

Recommended defensive actions

• Verify exposure of Vanus versions 0.8.0 through 0.9.0 in the environment
• Assess the authenticity of events published through the gateway CloudEvents HTTP receiver
• Implement authentication and authorization checks for event publication
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish versions, exploitation, impact, or remediation beyond what is provided, requiring verification from the supplied official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.