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.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
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.
A vulnerability (CWE-636) exists in openviking. Attackers reach the vulnerable code path via X-API-Key header without authentication.
Check the vendor advisory for the affected versions of openviking. Attack surface: X-API-Key header.
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to 0.3.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade openviking to 0.3.9ステージング環境で 0.3.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory disclosure@vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- exploit disclosure@vulncheck.com
- package github.com
- package pypi.org
- patch disclosure@vulncheck.com
- web disclosure@vulncheck.com