# CVE-2026-22681: OpenViking < 0.3.4 SSRF via /api/v1/resources

> Authenticated attackers can exploit SSRF in OpenViking to access internal network services and read sensitive data via crafted URLs.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-vh5m-r6vp-rxjg

## What is CVE-2026-22681?

CVE-2026-22681 is a high-severity server-side request forgery vulnerability in Volcengine OpenViking, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-22681?


## How do I fix CVE-2026-22681?

No fix has been published for CVE-2026-22681 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22681 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22681 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22681 and fix it if it is affected.

What it is: CVE-2026-22681 is a high-severity server-side request forgery vulnerability in Volcengine OpenViking, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22681 exists.

Affected product: Volcengine OpenViking. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22681/ (Markdown: https://insights.sbomify.com/CVE-2026-22681/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22681
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22681
- OSV: https://osv.dev/vulnerability/CVE-2026-22681

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22681/
Summaries are generated and may contain mistakes; the official description above is the record.