VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

shiva: vulnerability history, versions and safety

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

i
2 vulnerabilities recorded C1 U1
i
2 with no fix published

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

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

Most recent disclosure 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all shiva vulnerabilities

Vulert verdict on shiva 0.10.0 i

Updated on 23 Oct 2026

Careful: 0.10.0 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 44/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

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.10.0 — affected i
  • Vulnerabilities on record 2 over 3 years · 1 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 2 i
  • Stars 550 i
  • OpenSSF scorecard 1/10 i
  • Last release 135 months ago i
  • Licence MIT 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 shiva, 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.10.0 27 Jun 2015 C1 U1 MIT No Details →
0.9.0 17 Aug 2014 C1 U1 MIT No Details →
0.8.0 09 Oct 2013 C1 U1 MIT No Details →
0.7.0 17 Jul 2013 C1 U1 MIT No Details →
0.6.0 02 Jun 2013 C1 U1 MIT No Details →
0.5.0 16 May 2013 C1 U1 MIT No Details →
0.4.0 01 May 2013 C1 U1 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for shiva

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-31558: Absolute Path Traversal in shiva 9.3 critical No fix published 12 Jul 2022
CVE-2022-31558: Tooxie Shiva 0.10.0 Absolute Path Traversal Vulnerability 9.3 critical No fix published 29 Jun 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 shiva

Is shiva safe to use?

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

What is shiva's Vulert package health score?

Vulert scores shiva 44/100, which reads as risky. 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 shiva affected?

Yes. 0.10.0, 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 shiva have?

2 vulnerabilities are recorded for shiva in the PyPI ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 1 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 shiva vulnerabilities disclosed?

1 vulnerability was recorded for shiva in the last 12 months, and the oldest entry in this database dates to 12 Jul 2022. 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 shiva 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 shiva for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the shiva version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.