# CVE-2026-22680: OpenViking < 0.3.3 Missing Authorization via Task Polling

> Unauthenticated attackers can access task polling endpoints to retrieve sensitive background task metadata and result payloads from other users.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Apr 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-h336-2wxm-pr6q, PYSEC-2026-2855

## What is CVE-2026-22680?

CVE-2026-22680 is a medium-severity missing authorization vulnerability in Volcengine OpenViking, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenViking versions prior to 0.3.3 contain a missing authorization vulnerability in the task polling endpoints that allows unauthorized attackers to enumerate or retrieve background task metadata created by other users. Attackers can access the /api/v1/tasks and /api/v1/tasks/{task_id} routes without authentication to expose task type, task status, resource identifiers, archive URIs, result payloads, and error information, potentially causing cross-tenant interference in multi-tenant deployments.

Weakness: CWE-862 (Missing Authorization)

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

3 open source packages ship an affected version, including openviking and OpenViking. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openviking` | PyPI | All versions | 0.3.3 |
| `openviking` | PyPI | All versions | 0.3.3 |
| `OpenViking` | PyPI | All versions | 0.3.3 |

Products: Volcengine Openviking.

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

Upgrade openviking to 0.3.3 or later.

## Is CVE-2026-22680 being exploited?

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

## Other vulnerabilities in Volcengine OpenViking

- [CVE-2026-40525](https://insights.sbomify.com/CVE-2026-40525/): OpenViking < 0.3.9 Authentication Bypass via VikingBot OpenAPI (critical 9.1)
- [CVE-2026-28518](https://insights.sbomify.com/CVE-2026-28518/): OpenViking .ovpack Import ZIP Slip Path Traversal (high 8.4)
- [CVE-2026-34999](https://insights.sbomify.com/CVE-2026-34999/): OpenViking 0.2.5 < 0.2.14 Bot Proxy Endpoints Allow Unauthenticated Access (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22680 is a medium-severity missing authorization vulnerability in Volcengine OpenViking, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22680 exists.

Affected packages and fixed versions:
- openviking (PyPI): affected all versions; fixed in 0.3.3
- openviking (PyPI): affected all versions; fixed in 0.3.3
- OpenViking (PyPI): affected all versions; fixed in 0.3.3

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-22680/ (Markdown: https://insights.sbomify.com/CVE-2026-22680/index.md)
```

## Sources

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

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