VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

eve: vulnerability history, versions and safety

eve is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 28 releases, from Mar 2018 to Jul 2018. 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
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all eve vulnerabilities

Vulert verdict on eve 2.3.1 i

Updated on 23 Oct 2026

Good news: 2.3.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 72/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 2.3.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.3.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.3.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 12 Jul 2018 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 17 packages i
  • Stars 6,748 i
  • OpenSSF scorecard 2/10 i
  • Last release 6 months ago i
  • Licence non-standard 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 eve, 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
2.3.1 24 Mar 2026 none non-standard — Details →
2.3.0 19 Mar 2026 none non-standard — Details →
2.2.5 11 Feb 2026 none non-standard — Details →
2.2.4 02 Dec 2025 none non-standard — Details →
2.2.3 26 Aug 2025 none non-standard — Details →
2.2.2 26 Aug 2025 none non-standard — Details →
2.2.1 03 Jun 2025 none non-standard — Details →
2.2.0 15 Oct 2024 none non-standard — Details →
2.1.0 14 Mar 2023 none non-standard — Details →
2.0.4 10 Nov 2022 none non-standard — Details →
2.0.3 02 Nov 2022 none non-standard — Details →
2.0.2 23 Sep 2022 none non-standard — Details →
2.0.1 07 Sep 2022 none non-standard — Details →
2.0.0 01 Aug 2022 none non-standard — Details →
1.1.5 25 Jan 2021 none non-standard — Details →
1.1.4 22 Oct 2020 none non-standard — Details →
1.1.3 19 Sep 2020 none non-standard — Details →
1.1.2 09 Jul 2020 none non-standard — Details →
1.1.1 10 May 2020 none non-standard — Details →
1.1.0 07 Feb 2020 none non-standard — Details →
1.0.1 26 Jan 2020 none non-standard — Details →
1.0.0 19 Dec 2019 none non-standard — Details →
0.9.2 14 Jun 2019 none non-standard — Details →
0.9.1 14 Jun 2019 none non-standard — Details →
0.9.0 11 Apr 2019 none non-standard — Details →
0.8.1 04 Oct 2018 none non-standard — Details →
0.7.10 15 Jul 2018 none non-standard — Details →
0.8.0 10 May 2018 none non-standard — Details →
0.7.9 10 May 2018 none non-standard — Details →
0.7.8 07 Feb 2018 none non-standard — Details →
0.7.7 07 Feb 2018 none non-standard — Details →
0.7.6 14 Jan 2018 none non-standard — Details →
0.7.5 04 Dec 2017 none non-standard — Details →
0.7.4 24 May 2017 C1 U1 non-standard Yes Details →
0.7.3 03 May 2017 C1 U1 non-standard Yes Details →
0.7.2 06 Mar 2017 C1 U1 non-standard Yes Details →
0.7.1 14 Feb 2017 C1 U1 non-standard Yes Details →
0.7.0 06 Feb 2017 C1 non-standard Yes Details →
0.6.4 08 Jun 2016 C1 U1 non-standard Yes Details →
0.6.3 16 Mar 2016 C1 U1 non-standard Yes Details →
0.6.2 14 Mar 2016 C1 U1 non-standard Yes Details →
0.6.1 29 Oct 2015 C1 U1 non-standard Yes Details →
0.6.0 28 Sep 2015 C1 non-standard Yes Details →
0.5.3 17 Mar 2015 C1 U1 non-standard Yes Details →
0.5.2 23 Feb 2015 C1 U1 non-standard Yes Details →
0.5.1 16 Jan 2015 C1 U1 non-standard Yes Details →
0.5.0 12 Jan 2015 C1 non-standard Yes Details →
0.4.0 20 Jun 2014 C1 — Yes Details →
0.3.0 14 Feb 2014 C1 — Yes Details →
0.2.0 30 Nov 2013 C1 — Yes Details →
0.1.1 31 Oct 2013 C1 U1 — Yes Details →
0.1.0 30 Sep 2013 C1 — Yes Details →
0.0.9 29 Aug 2013 C1 U1 — Yes Details →
0.0.8 25 Jul 2013 C1 U1 — Yes Details →
0.0.7 18 Jun 2013 C1 U1 — Yes Details →
0.0.6 13 May 2013 C1 U1 — Yes Details →
0.0.5 11 Apr 2013 C1 U1 — Yes Details →
0.0.4 25 Feb 2013 C1 U1 — Yes Details →
0.0.3 22 Jan 2013 C1 U1 — Yes Details →
0.0.2 27 Nov 2012 C1 U1 — Yes Details →
0.0.1 20 Nov 2012 C1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2

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

03 Vulnerabilities

Recorded vulnerabilities for eve

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-8097: Code Injection in Eve Package 9.8 critical 0.7.5 12 Jul 2018
CVE-2018-8097: Code Injection in Eve (pyeve) N/A unrated f8f7019ffdf9b4e05faf95e1f04e204aa4c91f98 14 Mar 2018

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 eve

Is eve safe to use?

Vulert records 2 vulnerabilities for eve in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is eve's Vulert package health score?

Vulert scores eve 72/100, which reads as in good shape. 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).

Is the latest version of eve affected?

No. 2.3.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of eve should I use?

2.3.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does eve have?

2 vulnerabilities are recorded for eve 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 eve vulnerabilities disclosed?

0 vulnerabilities were recorded for eve in the last 12 months, and the oldest entry in this database dates to 14 Mar 2018. 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 eve 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 eve for upcoming vulnerabilities?

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