dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-22207

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-26
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenViking through version 0.1.18 contains a broken access control vulnerability where the absence of the root_api_key configuration disables authentication checks entirely. Unauthenticated attackers can directly access administrative endpoints that should require authentication, enabling account management, resource operations, and system configuration changes with ROOT privileges.

MitigationEnsure the root_api_key configuration is properly set in production deployments, or update to the patched version/commit 0251c70 that enforces authentication regardless of configuration state.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenViking installation
    Locate the OpenViking application installation directory and confirm the product name matches 'OpenViking'
    Affected if OpenViking is present on the system
  2. Determine installed version
    Check the application version from its metadata, version file, or package manager output and compare to 0.1.18
    Affected if Version is 0.1.18 or earlier
  3. Locate configuration file
    Find the configuration file where OpenViking stores runtime settings - this is typically a config file, .env file, or settings file in the application directory
    Affected if Configuration file exists and is accessible
  4. Check root_api_key configuration
    Inspect the configuration file for the presence and value of the root_api_key setting - verify whether it is set to a non-empty value or is completely absent/undefined
    Affected if root_api_key is either missing from configuration or set to an empty/null value
  5. Test authentication on admin endpoints
    Send a request to an administrative endpoint (such as /admin, /api/admin, or similar) without providing any authentication credentials and observe whether access is granted
    Affected if Unauthenticated requests to admin endpoints succeed without authentication failure

The environment is affected if OpenViking version 0.1.18 or earlier is running AND the root_api_key configuration is either absent or set to an empty value, allowing unauthenticated access to administrative functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Ensure the root_api_key configuration is properly set in production deployments, or update to the patched version/commit 0251c70 that enforces authentication regardless of configuration state.

Recommended fix Moderate confidence
  1. 1. Navigate to the OpenViking repository at https://github.com/volcengine/OpenViking
  2. 2. Locate the vulnerable version (0.1.18 or earlier)
  3. 3. Apply the fix by cherry-picking or merging commit 0251c7045b3f8092c4d2e1565115b1ba23db282f
  4. 4. Alternatively, ensure the root_api_key configuration is properly set in the deployment configuration
  5. 5. Verify that unauthenticated requests to protected endpoints are now rejected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22207 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22207 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data