CVE-2026-22207

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-02-26. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

February 26, 2026

Last Modified

July 14, 2026

Advisory Details (4)

Auto-updated Sep 19, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
generic

OpenViking Missing root_api_key Allows Anonymous ROOT Access | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openviking-missing-root-api-key-allows-anonymous-root-access
github_commit

commit 0251c7045b3f (volcengine/OpenViking)

Fix landed in volcengine/OpenViking commit 0251c7045b3f — awaiting tagged release

https://github.com/volcengine/OpenViking/commit/0251c7045b3f8092c4d2e1565115b1ba23db282f
github_pr

fix(server): 未配置 root_api_key 时仅允许 localhost 绑定

Fix merged in volcengine/OpenViking PR #310 on 2026-02-26 — awaiting tagged release

https://github.com/volcengine/OpenViking/pull/310
generic

[Bug]: Missing `root_api_key` enables anonymous ROOT access (broken access control) · Issue #302 · volcengine/OpenViking · GitHub

https://github.com/volcengine/OpenViking/issues/302

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 212 total refreshes for this CVE.

  1. 2026-09-19 21:51 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-09-01 01:04 UTCOSV refresh
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-15 01:16 UTCGHSA enrichment
  9. 2026-08-14 21:09 UTCGHSA enrichment
  10. 2026-08-14 13:01 UTCGHSA enrichment
  11. 2026-08-14 08:54 UTCEG score recompute
  12. 2026-08-14 08:54 UTCGHSA enrichment
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 00:52 UTCEG score recompute
  15. 2026-08-13 00:52 UTCGHSA enrichment
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 23:48 UTCEG score recompute
  18. 2026-08-11 23:48 UTCGHSA enrichment
  19. 2026-08-11 13:42 UTCEPSS rescore
  20. 2026-08-11 06:15 UTCEG score recompute
  21. 2026-08-11 06:15 UTCGHSA enrichment
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 13:12 UTCGHSA enrichment
  24. 2026-08-10 08:39 UTCGHSA enrichment
  25. 2026-08-10 02:12 UTCGHSA enrichment
  26. 2026-08-09 22:03 UTCGHSA enrichment
  27. 2026-08-09 17:56 UTCGHSA enrichment
  28. 2026-08-09 13:48 UTCEG score recompute
  29. 2026-08-09 13:48 UTCGHSA enrichment
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-09 08:33 UTCEG score recompute
  32. 2026-08-09 08:33 UTCGHSA enrichment
  33. 2026-08-08 16:37 UTCEPSS rescore
  34. 2026-08-08 08:55 UTCGHSA enrichment
  35. 2026-08-08 04:49 UTCGHSA enrichment
  36. 2026-08-08 00:41 UTCGHSA enrichment
  37. 2026-08-07 20:34 UTCEG score recompute
  38. 2026-08-07 20:34 UTCGHSA enrichment
  39. 2026-08-06 13:46 UTCEPSS rescore
  40. 2026-08-06 07:03 UTCGHSA enrichment
  41. 2026-08-06 02:57 UTCEG score recompute
  42. 2026-08-06 02:57 UTCGHSA enrichment
  43. 2026-08-05 19:17 UTCEPSS rescore
  44. 2026-08-04 15:10 UTCEPSS rescore
  45. 2026-08-04 10:38 UTCEPSS rescore
  46. 2026-08-04 04:57 UTCEG score recompute
  47. 2026-08-04 04:57 UTCGHSA enrichment
  48. 2026-08-03 10:35 UTCEPSS rescore
  49. 2026-08-02 23:33 UTCGHSA enrichment
  50. 2026-08-02 19:27 UTCEG score recompute
  51. 2026-08-02 19:27 UTCGHSA enrichment
  52. 2026-08-02 02:26 UTCEPSS rescore
  53. 2026-08-01 04:15 UTCEPSS rescore
  54. 2026-07-30 01:30 UTCEPSS rescore
  55. 2026-07-27 14:13 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 14:54 UTCEPSS rescore
  58. 2026-07-25 14:17 UTCEPSS rescore
  59. 2026-07-25 14:17 UTCEPSS rescore
  60. 2026-07-24 14:17 UTCEPSS rescore
  61. 2026-07-23 14:18 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 03:06 UTCEG score recompute
  64. 2026-07-22 14:08 UTCEPSS rescore
  65. 2026-07-21 15:24 UTCEPSS rescore
  66. 2026-07-21 15:24 UTCEPSS rescore
  67. 2026-07-20 17:08 UTCEPSS rescore
  68. 2026-07-19 14:31 UTCEPSS rescore
  69. 2026-07-19 14:31 UTCEPSS rescore
  70. 2026-07-19 02:29 UTCEPSS rescore
  71. 2026-07-19 02:28 UTCEPSS rescore
  72. 2026-07-18 10:04 UTCEPSS rescore
  73. 2026-07-18 10:04 UTCEPSS rescore
  74. 2026-07-17 18:29 UTCOSV refresh
  75. 2026-07-16 17:03 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-22207?
CVE-2026-22207 is a critical vulnerability published on February 26, 2026. 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 rootapikey configuration is omitted. Attackers can send requests to protected endpoints without authentication headers to…
When was CVE-2026-22207 disclosed?
CVE-2026-22207 was first published in the National Vulnerability Database on February 26, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-22207 actively exploited?
CVE-2026-22207 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.2% of all scored CVEs.
What is the CVSS score of CVE-2026-22207?
CVE-2026-22207 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-22207?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22207, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-22207

Explore →

Is Your Infrastructure Affected by CVE-2026-22207?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs