Is CVE-2026-22680 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-22680 being exploited in the wild.

How severe is CVE-2026-22680?

Medium severity, with a CVSS score of 5.3, published 7 April 2026.

Which products and versions are affected?

openviking (PyPI) ECOSYSTEM:introduced=0,fixed=0.3.3.

Is there a fix for CVE-2026-22680?

Yes. openviking (PyPI): upgrade to 0.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-22680 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-22680?

Check whether you run openviking (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-22680: Volcengine OpenViking missing authorization in task polling endpoints

CVE-2026-22680 · Severity: medium · CVSS 5.3 · Published 2026-04-07

OpenViking, an open-source framework for building AI-native applications, contains a security flaw in how it handles background tasks. Unauthorized users can access internal task information, including task status, result payloads, and resource identifiers, which should normally be private. This could allow an attacker to see what other users are doing or interfere with operations in environments where multiple customers share the same system.

Technologies: openviking (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-22680 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-22680 being exploited in the wild.
How severe is CVE-2026-22680?: Medium severity, with a CVSS score of 5.3, published 7 April 2026.
Which products and versions are affected?: openviking (PyPI) ECOSYSTEM:introduced=0,fixed=0.3.3.
Is there a fix for CVE-2026-22680?: Yes. openviking (PyPI): upgrade to 0.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-22680 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-22680?: Check whether you run openviking (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

openviking (PyPI): upgrade to 0.3.3 or later
```
pip install "openviking>=0.3.3"
```

Technical details

A missing authorization vulnerability (CWE-862) exists in OpenViking's task polling endpoints (/api/v1/tasks and /api/v1/tasks/{task_id}). The root cause is that these routes were mounted without request context validation, and the TaskTracker component stored tasks in a global namespace without ownership metadata. An unauthenticated remote attacker can exploit this to enumerate background tasks and retrieve sensitive metadata, including task types, status, resource identifiers, archive URIs, and result payloads. In multi-tenant deployments, this also allows for cross-tenant interference during asynchronous reindexing tasks. The issue is resolved in version 0.3.3 by enforcing end-to-end task ownership and requiring authentication for polling endpoints.

Affected products

Volcengine OpenViking < 0.3.3

Identifiers

CVE-2026-22680
GHSA-h336-2wxm-pr6q
PYSEC-2026-2855

Timeline

2026-04-02: disclosed: Pull request submitted to fix ownership leakage
2026-04-03: patched: Version 0.3.3 released with security fixes
2026-04-07: advisory: CVE-2026-22680 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.