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.
Security readout for executives and security teams
Plain-English summary
OpenViking can unintentionally grant full ROOT-level access when the root_api_key setting is missing. An unauthenticated remote attacker could reach administrative capabilities such as account management, resource operations, and system configuration. This is a critical access-control failure for any exposed OpenViking deployment through 0.1.18 before the fixing commit.
Executive priority
Treat this as urgent for any OpenViking deployment. The vulnerable state can turn missing configuration into unauthenticated administrative access, creating direct risk to accounts, resources, and system settings. Prioritize exposed systems first, then internal deployments.
Technical view
CVE-2026-22207 is a CWE-306 missing authentication flaw in Volcengine OpenViking. If root_api_key is omitted, protected endpoints may accept requests without authentication headers and treat the requester as ROOT. The CVSS 3.1 score is 9.8, reflecting network attackability, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Highest concern is internet-accessible or broadly reachable OpenViking instances through 0.1.18, prior to commit 0251c7045b3f8092c4d2e1565115b1ba23db282f, where root_api_key is omitted. Internal-only deployments still matter because compromise would provide administrative control over the service.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. However, the issue, pull request, patch commit, and third-party advisory are public, and the flaw requires no credentials when the vulnerable configuration exists.
Researcher notes
The provided sources identify the vulnerable condition, affected range, CWE, CVSS, and fixing commit. They do not provide a named fixed release in the bundle, so map the commit to the vendor’s current release before closing remediation tickets.
Mitigation direction
Apply commit 0251c7045b3f8092c4d2e1565115b1ba23db282f or a later vendor release.
Confirm root_api_key is configured and not omitted.
Restrict network access to OpenViking administrative endpoints until remediated.
Review the vendor issue, pull request, and advisory for updated guidance.
Validation and detection
Inventory all OpenViking deployments and record exact version or commit.
Identify instances through 0.1.18 or before the fixing commit.
Review configuration for missing root_api_key values.
In an authorized test environment, confirm protected endpoints reject unauthenticated requests.
Check logs for unauthenticated access attempts to administrative endpoints.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.