CVE-2026-22681

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-21. The CNA's CVSS baseline 8.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated
8.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

OpenViking before 0.3.4 contains a server-side request forgery vulnerability that allows authenticated low-privilege attackers to access internal network services by submitting arbitrary URLs to the resources API endpoint. Attackers can POST a crafted URL to /api/v1/resources, causing the server to issue outbound HEAD and GET requests with redirects enabled to loopback, RFC 1918, link-local, or cloud metadata addresses, then read back responses through normal content APIs to enumerate and interact with internal services.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
54
EG Risk 54/100

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 (value × EchelonGraph’s weight)
Severity85% × 45%
The EG Score, 8.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 21, 2026

Last Modified

October 1, 2026

Advisory Details (4)

Auto-updated Aug 21, 2026
Patch available. Sources: github_commit, github_pr, github_release.
Web page

OpenViking < 0.3.4 SSRF via /api/v1/resources | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openviking-ssrf-via-api-v1-resources
GitHub release Patch Available

v0.3.4

Patch available: volcengine/OpenViking v0.3.4

https://github.com/volcengine/OpenViking/releases/tag/v0.3.4
GitHub pull request

fix security: feat(resources): harden HTTP resource ingestion against private-network SSRF

Fix merged in volcengine/OpenViking PR #1133 on 2026-04-05 — awaiting tagged release

https://github.com/volcengine/OpenViking/pull/1133
GitHub commit

commit 41e345896d24 (volcengine/OpenViking)

Fix landed in volcengine/OpenViking commit 41e345896d24 — awaiting tagged release

https://github.com/volcengine/OpenViking/commit/41e345896d247e43ab78bbcb38b4a5b1b38ef62c

Vendor Advisories for CVE-2026-22681(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 95× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 181 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 81 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-22681?
CVE-2026-22681 is a high-severity vulnerability; its CVE record was published on August 21, 2026. OpenViking before 0.3.4 contains a server-side request forgery vulnerability that allows authenticated low-privilege attackers to access internal network services by submitting arbitrary URLs to the resources API endpoint. Attackers can POST a crafted URL to /api/v1/resources, causing the server to…
When was CVE-2026-22681 made public?
CVE-2026-22681 was made public on March 31, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 21, 2026. EchelonGraph's copy of the record carries a last-modified date of October 1, 2026; the record at its source may have been updated since.
Is CVE-2026-22681 actively exploited?
CVE-2026-22681 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-22681?
CVE-2026-22681 has a CVSS base score of 8.5 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-22681?
A fix for CVE-2026-22681 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-22681 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-22681?

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

Book a Demo →Browse All CVEs