← Back
CVE-2026-40525
critical
CVSS 9.1
Vulnerability in openviking (CVE-2026-40525)
Summary
vulnerability in openviking (CVE-2026-40525). Confidential information can be exposed externally. Exploitable via `X-API-Key header`. Mitigation: upgrade to `0.3.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40525** has been found in openviking.
Attackers can target a specific entry point like `X-API-Key header` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade openviking to **0.3.9** or later.
If unsure, ask your IT team or search "openviking CVE-2026-40525" on the vendor's site.
CVE-2026-40525 (openviking) — CWE-636 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: X-API-Key header
Patched: `0.3.9` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-636) exists in openviking. Attackers reach the vulnerable code path via `X-API-Key header` without authentication.
📍 Affected scope
openviking — . Attack surface: X-API-Key header.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.3.9**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'openviking' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'openviking' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `openviking` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade openviking to 0.3.9ステージング環境で 0.3.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
openviking
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.9"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-40525
- advisory https://github.com/advisories/GHSA-jgq2-vq69-gr6h
- package https://github.com/volcengine/OpenViking
- package https://pypi.org/project/openviking
- web https://github.com/volcengine/OpenViking/commit/c7bb1676f4d037609f041bf39e4e2bd52e8f9820
- web https://github.com/volcengine/OpenViking/pull/1447
- web https://github.com/volcengine/OpenViking/releases/tag/v0.3.9
- web https://www.vulncheck.com/advisories/openviking-authentication-bypass-via-vikingbot-openapi