# OpenViking: Unauthenticated remote bot control via OpenAPI HTTP routes

Advisory record · `GHSA-jgq2-vq69-gr6h`

- **Identifiers:** `GHSA-jgq2-vq69-gr6h` · `CVE-2026-40525` · `PYSEC-2026-438`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-636](https://cwe.mitre.org/data/definitions/636.html)
- **Tags:** [CWE-636](https://agentprime.io/advisories/tag/cwe-636.md)
- **Published:** 17 Apr 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 Apr 2026, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `openviking` (PyPI): affected `<0.3.9`; fixed in `0.3.9`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> OpenViking versions before 0.3.9 are vulnerable to an authentication bypass in the VikingBot OpenAPI HTTP routes: when the api_key setting is unset or empty, the authentication check fails open. A remote attacker with network access to the exposed service can use bot-control functions without a valid X-API-Key header, including submitting prompts, managing bot sessions, and reaching tools, integrations, and data the bot can access. Upgrade to OpenViking 0.3.9 or later. Setting a non-empty api_key is a workaround if upgrading is not possible.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.1 Critical, CVSS 4.0: `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`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0057, the 47th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jgq2-vq69-gr6h)

## Sources

- [GitHub Advisory Database: GHSA-jgq2-vq69-gr6h](https://github.com/advisories/GHSA-jgq2-vq69-gr6h)
- [OSV: GHSA-jgq2-vq69-gr6h](https://osv.dev/vulnerability/GHSA-jgq2-vq69-gr6h)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-40525>
- <https://github.com/volcengine/OpenViking/pull/1447>
- <https://github.com/volcengine/OpenViking/commit/c7bb1676f4d037609f041bf39e4e2bd52e8f9820>
- <https://github.com/volcengine/OpenViking>
- <https://github.com/volcengine/OpenViking/releases/tag/v0.3.9>
- <https://www.vulncheck.com/advisories/openviking-authentication-bypass-via-vikingbot-openapi>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jgq2-vq69-gr6h>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jgq2-vq69-gr6h/>. Everything for agents: <https://agentprime.io/llms.txt>.