# CVE-2026-22207: OpenViking Missing root_api_key Allows Anonymous ROOT Access

> Unauthenticated attackers can gain root privileges if the root_api_key is omitted, allowing full administrative control over the OpenViking server.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** No
- **Published:** 26 Feb 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-mpqv-244m-cf9r

## What is CVE-2026-22207?

CVE-2026-22207 is a critical missing authorization vulnerability in Volcengine OpenViking, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenViking through version 0.1.18, prior to commit 0251c70, contains a broken access control vulnerability that allows unauthenticated attackers to gain ROOT privileges when the root_api_key configuration is omitted. Attackers can send requests to protected endpoints without authentication headers to access administrative functions including account management, resource operations, and system configuration.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

No fix has been published for CVE-2026-22207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22207 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22207 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22207 is a critical missing authorization vulnerability in Volcengine OpenViking, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22207 exists.

Affected product: Volcengine OpenViking. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-22207/ (Markdown: https://insights.sbomify.com/CVE-2026-22207/index.md)
```

## Sources

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

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