Vulnerability Database · PyPI · openviking · Version
openviking 0.2.10.dev50
0.2.10.dev50 is affected by 6 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 2 High 2 Medium 2 Low 0 Unrated 0
-
Released 23 Mar 2026
Licence Apache-2.0
Also known from other sources 4
Newer releases 59
Database updated 23/Oct/2026
Release and licence data published by PyPI. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
openviking 0.2.10.dev50 vulnerabilities
6 vulnerabilities cover openviking 0.2.10.dev50. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-40525: OpenViking Unauthenticated Remote Bot Control Vulnerability | 9.1 critical | 0.3.9 | 29 Jun 2026 |
| CVE-2026-40525: OpenViking Unauthenticated Remote Bot Control Vulnerability | 9.1 critical | 0.3.9 | 17 Apr 2026 |
| CVE-2026-28518: OpenViking Path Traversal Vulnerability | 7.8 high | No fix published | 13 Jul 2026 |
| CVE-2026-28518: OpenViking Path Traversal Vulnerability | 7.8 high | No fix published | 03 Mar 2026 |
| CVE-2026-22680: OpenViking Missing Authorization Vulnerability in Task Polling Endpoints | 5.3 medium | 0.3.3 | 13 Jul 2026 |
| CVE-2026-22680: OpenViking Task Polling Endpoint Missing Authorization Vulnerability | 5.3 medium | 0.3.3 | 07 Apr 2026 |
Looking for another version, or everything Vulert holds for openviking?
Questions
About openviking 0.2.10.dev50
Is openviking 0.2.10.dev50 vulnerable?
Yes. 6 vulnerabilities in the Vulert database cover openviking 0.2.10.dev50: 2 critical, 2 high, 2 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.2.10.dev50 the latest release of openviking?
No. 0.2.10.dev50 was published 23 Mar 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor openviking for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the openviking version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.