OPENVIKING · CVE-2026-40525 · AI agents & MCP
FIX → 0.3.9
OpenViking's VikingBot OpenAPI HTTP routes skip the authentication check when the api_key setting is unset or empty. A remote attacker who can reach the service can send prompts, create bot sessions, and use the bot's tools, integrations and secrets without an X-API-Key header.
first public Apr 17, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running OpenViking with VikingBot's OpenAPI HTTP routes exposed on a network. The flaw applies when api_key is unset or empty, so a deployment with a non-empty api_key set is not affected by this bypass. Local-only deployments that are not reachable from the network are lower risk.
Not affected if api-key-set, not-network-exposed
Who cares ai-agents, openviking, python, vikingbot
pip show openviking and compare it to 0.3.9.api_key value and confirm it is set to a non-empty value.Upgrade to 0.3.9
OpenViking prior to commit c7bb167 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. Remote attackers with network access to the exposed service can invoke privileged bot-control functionality without providing 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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
openviking 0.3.9 (fixed version per the product data)GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.