VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

openviking: vulnerability history, versions and safety

openviking is a package in the PyPI ecosystem. Vulert records 6 vulnerabilities for it across 60 releases, from Mar 2026 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded C1 H1 M1 U3
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
6 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all openviking vulnerabilities

Vulert verdict on openviking 0.5.1.1 i

Updated on 23 Oct 2026

Careful: 0.5.1.1 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.5.1.1 — affected i
  • Vulnerabilities on record 6 over 1 year · 6 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 2 i
  • Depended on by 3 packages i
  • Stars 39,975 i
  • Last release this month i
  • Licence AGPL-3.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for openviking, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.5.1.1 20 Oct 2026 H1 U1 AGPL-3.0 No Details →
0.5.1 19 Oct 2026 H1 U1 AGPL-3.0 No Details →
0.5.0 09 Oct 2026 H1 U1 AGPL-3.0 No Details →
0.4.23 02 Oct 2026 H1 U1 AGPL-3.0 No Details →
0.4.22 28 Sep 2026 H1 U1 AGPL-3.0 No Details →
0.4.21 20 Sep 2026 H1 U1 AGPL-3.0 No Details →
0.4.20 14 Sep 2026 H1 U1 AGPL-3.0 No Details →
0.4.19 08 Sep 2026 H1 U1 AGPL-3.0 No Details →
0.4.18 08 Sep 2026 H1 U1 AGPL-3.0 No Details →
0.4.17.2.dev0 31 Aug 2026 H1 U1 AGPL-3.0 No Details →
0.4.17.1 31 Aug 2026 H1 U1 AGPL-3.0 No Details →
0.4.18.dev0 28 Aug 2026 H1 U1 AGPL-3.0 No Details →
0.4.17 28 Aug 2026 H1 U1 AGPL-3.0 No Details →
0.4.17.dev0 21 Aug 2026 H1 U1 AGPL-3.0 No Details →
0.4.16 21 Aug 2026 H1 U1 AGPL-3.0 No Details →
0.4.16.dev0 18 Aug 2026 H1 U1 AGPL-3.0 No Details →
0.4.15 18 Aug 2026 H1 U1 AGPL-3.0 No Details →
0.4.14 17 Aug 2026 H1 U1 AGPL-3.0 No Details →
0.4.13 06 Aug 2026 H1 U1 AGPL-3.0 No Details →
0.4.12 03 Aug 2026 H1 U1 AGPL-3.0 No Details →
0.4.11 23 Jul 2026 H1 U1 AGPL-3.0 No Details →
0.4.10 16 Jul 2026 H1 U1 AGPL-3.0 No Details →
0.4.9 13 Jul 2026 H1 U1 AGPL-3.0 No Details →
0.4.8 08 Jul 2026 H1 U1 AGPL-3.0 No Details →
0.4.7 02 Jul 2026 H1 U1 AGPL-3.0 No Details →
0.4.6 29 Jun 2026 H1 U1 AGPL-3.0 No Details →
0.4.5 24 Jun 2026 H1 U1 AGPL-3.0 No Details →
0.4.3 18 Jun 2026 H1 U1 AGPL-3.0 No Details →
0.4.2 17 Jun 2026 H1 U1 AGPL-3.0 No Details →
0.4.1 16 Jun 2026 H1 U1 AGPL-3.0 No Details →
0.3.24 05 Jun 2026 H1 U1 AGPL-3.0 No Details →
0.3.23 03 Jun 2026 H1 U1 AGPL-3.0 No Details →
0.3.22 29 May 2026 H1 U1 AGPL-3.0 No Details →
0.3.21 27 May 2026 H1 U1 AGPL-3.0 No Details →
0.3.20 25 May 2026 H1 U1 AGPL-3.0 No Details →
0.3.19 22 May 2026 H1 U1 AGPL-3.0 No Details →
0.3.18 22 May 2026 H1 U1 AGPL-3.0 No Details →
0.3.17 15 May 2026 H1 U1 AGPL-3.0 No Details →
0.3.16 09 May 2026 H1 U1 AGPL-3.0 No Details →
0.3.15 09 May 2026 H1 U1 AGPL-3.0 No Details →
0.3.14 30 Apr 2026 H1 U1 AGPL-3.0 No Details →
0.3.13 29 Apr 2026 H1 U1 AGPL-3.0 No Details →
0.3.12 24 Apr 2026 H1 U1 AGPL-3.0 No Details →
0.3.10 23 Apr 2026 H1 U1 AGPL-3.0 No Details →
0.3.9 18 Apr 2026 H1 U1 AGPL-3.0 No Details →
0.3.8 15 Apr 2026 C1 U1 AGPL-3.0 Yes Details →
0.3.6 14 Apr 2026 C1 U1 AGPL-3.0 Yes Details →
0.3.5 10 Apr 2026 C1 U1 AGPL-3.0 Yes Details →
0.3.4 09 Apr 2026 C1 U1 AGPL-3.0 Yes Details →
0.3.3 03 Apr 2026 C1 U1 AGPL-3.0 Yes Details →
0.3.2 01 Apr 2026 C1 M1 U2 AGPL-3.0 Yes Details →
0.3.1 31 Mar 2026 C1 M1 U2 AGPL-3.0 Yes Details →
0.2.15 30 Mar 2026 C1 M1 U2 AGPL-3.0 Yes Details →
0.2.13 26 Mar 2026 C1 M1 U2 Apache-2.0 Yes Details →
0.2.12 25 Mar 2026 C1 M1 U2 Apache-2.0 Yes Details →
0.2.11 25 Mar 2026 C1 M1 U2 Apache-2.0 Yes Details →
0.2.12.dev1 25 Mar 2026 C1 M1 U2 Apache-2.0 Yes Details →
0.2.10.dev50 23 Mar 2026 C1 M1 U2 Apache-2.0 Yes Details →
0.2.10.dev45 23 Mar 2026 C1 M1 U2 Apache-2.0 Yes Details →
0.3.11 — H1 U1 — No Details →

All 60 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 6 of the 6 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for openviking

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-40525: OpenViking Unauthenticated Remote Bot Control Vulnerability 9.1 critical 0.3.9 17 Apr 2026
CVE-2026-40525: OpenViking Unauthenticated Remote Bot Control Vulnerability 9.1 critical 0.3.9 29 Jun 2026
CVE-2026-28518: OpenViking Path Traversal Vulnerability 7.8 high No fix published 03 Mar 2026
CVE-2026-28518: OpenViking Path Traversal Vulnerability 7.8 high No fix published 13 Jul 2026
CVE-2026-22680: OpenViking Task Polling Endpoint Missing Authorization Vulnerability 5.3 medium 0.3.3 07 Apr 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About openviking

Is openviking safe to use?

Vulert records 6 vulnerabilities for openviking in PyPI: 1 critical, 1 high, 1 medium and 0 low, plus 3 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is openviking's Vulert package health score?

Vulert scores openviking 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of openviking affected?

Yes. 0.5.1.1, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does openviking have?

6 vulnerabilities are recorded for openviking in the PyPI ecosystem: 1 critical, 1 high, 1 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new openviking vulnerabilities disclosed?

6 vulnerabilities were recorded for openviking in the last 12 months, and the oldest entry in this database dates to 03 Mar 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of openviking are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.