CVE-2026-40525: CWE-636 Not Failing Securely ('Fail Open') in volcengine OpenViking
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. 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.
AI Analysis
Technical Summary
CVE-2026-40525 is an authentication bypass vulnerability in volcengine's OpenViking product affecting versions before 0.3.9. The issue arises because the VikingBot OpenAPI HTTP route fails to enforce authentication properly when the api_key configuration is unset or empty, effectively failing open. This allows remote attackers with network access to bypass authentication and perform privileged operations such as controlling the bot, submitting arbitrary prompts, creating or using bot sessions, and accessing sensitive downstream resources. The vulnerability is categorized under CWE-636 (Not Failing Securely). The CVSS 4.0 score is 9.1, indicating critical severity. No official patch or remediation level has been published yet, and no known exploits are reported in the wild.
Potential Impact
Successful exploitation allows unauthenticated remote attackers to bypass authentication controls and gain unauthorized access to privileged bot-control functionality. Attackers can submit arbitrary prompts, manipulate bot sessions, and access sensitive downstream tools, integrations, secrets, or data accessible to the bot. This could lead to significant confidentiality and integrity impacts on the affected system and its data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, ensure that the api_key configuration value is properly set and not left unset or empty to prevent the authentication check from failing open. Restrict network access to the VikingBot OpenAPI HTTP route to trusted users only as a temporary mitigation.
CVE-2026-40525: CWE-636 Not Failing Securely ('Fail Open') in volcengine OpenViking
Description
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. 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.
CVSS v4.0
Score 9.1critical
Affected software
pkg:github/volcengine/OpenVikingRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-40525 is an authentication bypass vulnerability in volcengine's OpenViking product affecting versions before 0.3.9. The issue arises because the VikingBot OpenAPI HTTP route fails to enforce authentication properly when the api_key configuration is unset or empty, effectively failing open. This allows remote attackers with network access to bypass authentication and perform privileged operations such as controlling the bot, submitting arbitrary prompts, creating or using bot sessions, and accessing sensitive downstream resources. The vulnerability is categorized under CWE-636 (Not Failing Securely). The CVSS 4.0 score is 9.1, indicating critical severity. No official patch or remediation level has been published yet, and no known exploits are reported in the wild.
Potential Impact
Successful exploitation allows unauthenticated remote attackers to bypass authentication controls and gain unauthorized access to privileged bot-control functionality. Attackers can submit arbitrary prompts, manipulate bot sessions, and access sensitive downstream tools, integrations, secrets, or data accessible to the bot. This could lead to significant confidentiality and integrity impacts on the affected system and its data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, ensure that the api_key configuration value is properly set and not left unset or empty to prevent the authentication check from failing open. Restrict network access to the VikingBot OpenAPI HTTP route to trusted users only as a temporary mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-04-13T20:29:02.810Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e27e0fbdfbbecc5978c959
Added to database: 04/17/2026, 18:38:07 UTC
Last enriched: 07/15/2026, 10:29:11 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 157
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.