CVE-2026-34999: OpenViking versions 0.2.5 prior to 0.2.14 contain a missing authentication vulnerability in the bot proxy rout

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2026-34999 is a medium-severity flaw (CVSS 5.3) affecting openviking. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

OpenViking versions 0.2.5 prior to 0.2.14 contain a missing authentication vulnerability in the bot proxy router that allows remote unauthenticated attackers to access protected bot proxy functionality by sending requests to the POST /bot/v1/chat and POST /bot/v1/chat/stream endpoints. Attackers can bypass authentication checks and interact directly with the upstream bot backend through the OpenViking proxy without providing valid credentials.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-306
Published	2026-04-01
Last modified	2026-10-26

Publisher (CNA): VulnCheck · Vendor: volcengine

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-01 14:16 UTCPublished CVE record published
2026-10-26 22:10 UTCUpdated Record last modified

volcengine openviking UPGRADE

Affected: >= 0.2.5 and < 0.2.14

Fixed in: 0.2.14

Safe to downgrade to: a release before 0.2.5

1. Check installed version

apt-cache policy openviking || rpm -q openviking || openviking --version

2. UPGRADE to 0.2.14 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade openviking

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade openviking

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 0.2.5 (Debian / Ubuntu)

apt-cache madison openviking sudo apt install openviking=<VERSION_BEFORE_0.2.5> sudo apt-mark hold openviking

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list openviking sudo dnf downgrade openviking-<VERSION_BEFORE_0.2.5> sudo dnf versionlock add openviking

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-34999?

openviking: upgrade to 0.2.14. Exact commands for each OS are on this page.

Is CVE-2026-34999 being exploited?

CVE-2026-34999 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-34999 affect?

CVE-2026-34999 affects openviking. Severity is medium (CVSS 5.3). OpenViking versions 0.2.5 prior to 0.2.14 contain a missing authentication vulnerability in the bot proxy router that allows remote unauthenticated attackers to access protected bot proxy functionality by sending requests to the POST /bot/v

How urgent is CVE-2026-34999?

Priority 33/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-22680 MEDIUM 5.3 UPGRADE OpenViking versions prior to 0.3.3 contain a missing authorization vulnerability in the task polling endpoints
CVE-2026-40525 CRITICAL 9.1 UPGRADE OpenViking prior to version 0.3.9 contains an authentication bypass vulnerability in the VikingBot OpenAPI HTT

References

← Back to latest CVEs