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.
CVE-2026-22681
HIGHPre-NVD 8.58.5Elevated
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.5Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.5
- EG Score
- 8.5(low)
- EG Risk
- 54(Track)EG Risk 54/100SSVC: Track
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 computedSeverity85% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 21, 2026
Last Modified
August 21, 2026
Advisory Details (4)
Auto-updated Aug 21, 2026Patch available. Sources: github_commit, github_pr, github_release.
generic
OpenViking < 0.3.4 SSRF via /api/v1/resources | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openviking-ssrf-via-api-v1-resourcesgithub_release Patch Available
v0.3.4
Patch available: volcengine/OpenViking v0.3.4
https://github.com/volcengine/OpenViking/releases/tag/v0.3.4github_pr
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/1133github_commit
commit 41e345896d24 (volcengine/OpenViking)
Fix landed in volcengine/OpenViking commit 41e345896d24 — awaiting tagged release
https://github.com/volcengine/OpenViking/commit/41e345896d247e43ab78bbcb38b4a5b1b38ef62cVendor 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 4× in last 7d / 4× 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.
- 2026-08-21 17:21 UTCEG score recompute
- 2026-08-21 17:05 UTCEG score recompute
- 2026-08-21 16:20 UTCEG score recompute
- 2026-08-21 16:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(4)
What is CVE-2026-22681?
CVE-2026-22681 is a high vulnerability 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 disclosed?
CVE-2026-22681 was first published in the National Vulnerability Database on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-22681?
CVE-2026-22681 has a CVSS v3 base score of 8.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-22681?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22681, 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-22681
Is Your Infrastructure Affected by CVE-2026-22681?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.