# CVE-2026-40525: OpenViking < 0.3.9 Authentication Bypass via VikingBot OpenAPI

> Remote attackers can bypass authentication in OpenViking VikingBot OpenAPI when API keys are unset, accessing privileged bot functions and sensitive data.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Apr 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-jgq2-vq69-gr6h, PYSEC-2026-438

## What is CVE-2026-40525?

CVE-2026-40525 is a critical authentication bypass vulnerability in volcengine OpenViking, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-636 (Not Failing Securely)

## Which versions are affected by CVE-2026-40525?

3 open source packages ship an affected version, including openviking. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openviking` | PyPI | All versions | 0.3.9 |
| `openviking` | PyPI | All versions | 0.3.9 |
| `openviking` | PyPI | All versions | 0.3.9 |

Products: Volcengine Openviking.

## How do I fix CVE-2026-40525?

Upgrade openviking to 0.3.9 or later.

## Is CVE-2026-40525 being exploited?

There is no known exploitation of CVE-2026-40525 in the wild and no public exploit code.

## Other vulnerabilities in volcengine OpenViking

- [CVE-2026-28518](https://insights.sbomify.com/CVE-2026-28518/): OpenViking .ovpack Import ZIP Slip Path Traversal (high 8.4)
- [CVE-2026-22680](https://insights.sbomify.com/CVE-2026-22680/): OpenViking < 0.3.3 Missing Authorization via Task Polling (medium 6.9)
- [CVE-2026-34999](https://insights.sbomify.com/CVE-2026-34999/): OpenViking 0.2.5 < 0.2.14 Bot Proxy Endpoints Allow Unauthenticated Access (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40525 and fix it if it is affected.

What it is: CVE-2026-40525 is a critical authentication bypass vulnerability in volcengine OpenViking, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40525 in the wild and no public exploit code.

Affected packages and fixed versions:
- openviking (PyPI): affected all versions; fixed in 0.3.9
- openviking (PyPI): affected all versions; fixed in 0.3.9
- openviking (PyPI): affected all versions; fixed in 0.3.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40525/ (Markdown: https://insights.sbomify.com/CVE-2026-40525/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40525
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40525
- OSV: https://osv.dev/vulnerability/CVE-2026-40525

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40525/
Summaries are generated and may contain mistakes; the official description above is the record.