Is CVE-2026-34999 exploited in the wild?

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

How severe is CVE-2026-34999?

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

Which products and versions are affected?

Volcengine OpenViking 0.2.5 to 0.2.13.

Is there a fix for CVE-2026-34999?

A patch was published on 2026-03-27: Fix merged into main branch via Pull Request 996 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34999 attacked?

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

Am I affected by CVE-2026-34999?

Check whether anything you run is named in the advisory. 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-34999: Volcengine OpenViking missing authentication in bot proxy router

CVE-2026-34999 · Severity: medium · CVSS 5.3 · Published 2026-04-01

OpenViking, an open-source platform for managing AI agents and bots, contains a security flaw in its bot proxy component. This vulnerability allows unauthorized individuals to bypass security checks and interact directly with connected AI backends without providing valid credentials. This could lead to unauthorized use of AI services and potential exposure of bot-related data.

Quick answers

Is CVE-2026-34999 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34999 being exploited in the wild.
How severe is CVE-2026-34999?: Medium severity, with a CVSS score of 5.3, published 1 April 2026.
Which products and versions are affected?: Volcengine OpenViking 0.2.5 to 0.2.13.
Is there a fix for CVE-2026-34999?: A patch was published on 2026-03-27: Fix merged into main branch via Pull Request 996 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34999 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-34999?: Check whether anything you run is named in the advisory. 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.

Technical details

A missing authentication vulnerability (CWE-306) exists in the OpenViking bot proxy router. The issue stems from the 'verify_auth' function being optional and non-blocking in the request pipeline for specific endpoints. A remote, unauthenticated attacker can exploit this by sending specially crafted POST requests to the '/bot/v1/chat' and '/bot/v1/chat/stream' endpoints. Successful exploitation allows the attacker to bypass authentication checks and interact directly with the upstream bot backend. The vulnerability is resolved in version 0.2.14 by enforcing mandatory token extraction and validation for these routes.

Affected products

Volcengine OpenViking 0.2.5 to 0.2.13

Timeline

2026-03-27: patched: Fix merged into main branch via Pull Request 996
2026-03-30: advisory: Official release of version 0.2.14 containing the fix
2026-04-01: disclosed: CVE published and NVD entry created

References

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