OpenViking prior to version 0.3.9 contains an authentication bypass vulnerability in the VikingBot OpenAPI HTTP route surface where the authentication check fails open when the api_key configuration value is unset or empty. This absence of authentication corresponds to CWE‑636 and permits any user to invoke privileged bot‑control functionality without supplying a valid X‑API‑Key header, including submitting attacker‑controlled prompts, creating or using bot sessions, and accessing downstream tools, integrations, secrets, or data accessible to the bot.

The vulnerability affects OpenViking deployments by Volcengine that use any version released before the commit c7bb1676. The exposed HTTP routes of the VikingBot OpenAPI allow unrestricted access to bot functionalities and any downstream tools, integrations, secrets, or data the bot can reach.

The CVSS score of 9.1 indicates high severity. The EPSS score of 0.00109 (approximately 0.109%) indicates an extremely low probability of exploitation, but the absence of a blocking check makes exploitation straightforward for attackers with network reach to the exposed service. Because the vulnerability is not listed in the CISA KEV catalog and no known exploits are publicly disclosed yet, the likelihood of immediate exploitation is uncertain, yet the potential impact of unauthorized bot actions remains high. Attackers would likely target the open route via standard HTTP requests, bypassing authentication entirely.