Vulnerability Database · PyPI · Package report

pymisp: vulnerability history, versions and safety

pymisp is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

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.

Vulert verdict on pymisp 2.5.34.4 i

Updated on 23 Oct 2026

Good news: 2.5.34.4, the version you would install today, has no known vulnerabilities.

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 2.5.34.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 36 packages i
  • Stars 494 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence BSD-2-Clause 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 pymisp, 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.5.34.4 17 Sep 2026 none BSD-2-Clause — Details →
2.5.34.3 10 Sep 2026 none BSD-2-Clause — Details →
2.5.34.2 14 Aug 2026 none BSD-2-Clause — Details →
2.5.34.1 28 Apr 2026 none BSD-2-Clause — Details →
2.5.34 28 Apr 2026 none BSD-2-Clause — Details →
2.5.33.2 21 Apr 2026 none BSD-2-Clause — Details →
2.5.33.1 03 Mar 2026 none BSD-2-Clause — Details →
2.5.33 27 Feb 2026 none BSD-2-Clause — Details →
2.5.32.3 16 Feb 2026 none BSD-2-Clause — Details →
2.5.32.2 02 Feb 2026 none BSD-2-Clause — Details →
2.5.32.1 02 Feb 2026 none BSD-2-Clause — Details →
2.5.32 14 Jan 2026 none BSD-2-Clause — Details →
2.5.17.3 25 Nov 2025 none BSD-2-Clause — Details →
2.5.17.2 24 Sep 2025 none BSD-2-Clause — Details →
2.5.17.1 15 Sep 2025 none BSD-2-Clause — Details →
2.5.17 04 Aug 2025 none BSD-2-Clause — Details →
2.5.12 13 May 2025 none BSD-2-Clause — Details →
2.5.10 04 Apr 2025 none BSD-2-Clause — Details →
2.5.9 26 Mar 2025 none BSD-2-Clause — Details →
2.5.8.1 18 Mar 2025 none BSD-2-Clause — Details →
2.5.8 18 Mar 2025 none BSD-2-Clause — Details →
2.5.7.1 22 Feb 2025 none BSD-2-Clause — Details →
2.5.7 20 Feb 2025 none BSD-2-Clause — Details →
2.5.4 20 Dec 2024 none BSD-2-Clause — Details →
2.5.3 16 Dec 2024 none BSD-2-Clause — Details →
2.5.2 18 Nov 2024 none BSD-2-Clause — Details →
2.5.2.dev2 15 Nov 2024 none BSD-2-Clause — Details →
2.5.2.dev1 13 Nov 2024 none BSD-2-Clause — Details →
2.5.2.dev0 11 Nov 2024 none BSD-2-Clause — Details →
2.5.1 17 Oct 2024 none BSD-2-Clause — Details →
2.5.0 04 Oct 2024 none BSD-2-Clause — Details →
2.4.198 13 Sep 2024 none BSD-2-Clause — Details →
2.4.197 02 Sep 2024 none BSD-2-Clause — Details →
2.4.196 21 Aug 2024 none BSD-2-Clause — Details →
2.4.195 27 Jul 2024 none BSD-2-Clause — Details →
2.4.194 21 Jun 2024 none BSD-2-Clause — Details →
2.4.193 07 Jun 2024 none BSD-2-Clause — Details →
2.4.190 18 Apr 2024 none BSD-2-Clause — Details →
2.4.188 22 Mar 2024 none BSD-2-Clause — Details →
2.4.187 07 Mar 2024 none BSD-2-Clause — Details →
2.4.186 29 Feb 2024 none BSD-2-Clause — Details →
2.4.185 17 Feb 2024 none BSD-2-Clause — Details →
2.4.184.3 12 Feb 2024 none BSD-2-Clause — Details →
2.4.184.2 06 Feb 2024 none BSD-2-Clause — Details →
2.4.184.1 06 Feb 2024 none BSD-2-Clause — Details →
2.4.184 02 Feb 2024 none BSD-2-Clause — Details →
2.4.183 04 Jan 2024 none BSD-2-Clause — Details →
2.4.182 14 Dec 2023 none BSD-2-Clause — Details →
2.4.179 23 Nov 2023 none BSD-2-Clause — Details →
2.4.178 24 Oct 2023 none BSD-2-Clause — Details →
2.4.176 15 Sep 2023 none BSD-2-Clause — Details →
2.4.175 24 Aug 2023 none BSD-2-Clause — Details →
2.4.174 31 Jul 2023 none BSD-2-Clause — Details →
2.4.173 18 Jul 2023 none BSD-2-Clause — Details →
2.4.172 09 Jun 2023 none BSD-2-Clause — Details →
2.4.171 16 May 2023 none BSD-2-Clause — Details →
2.4.170.2 04 May 2023 none BSD-2-Clause — Details →
2.4.170.1 19 Apr 2023 none BSD-2-Clause — Details →
2.4.170 12 Apr 2023 none BSD-2-Clause — Details →
2.4.169.3 27 Mar 2023 none BSD-2-Clause — Details →
2.4.169.2 17 Mar 2023 none BSD-2-Clause — Details →
2.4.169.1 14 Mar 2023 none BSD-2-Clause — Details →
2.4.169 14 Mar 2023 none BSD-2-Clause — Details →
2.4.168.1 28 Feb 2023 none BSD-2-Clause — Details →
2.4.168 23 Jan 2023 none BSD-2-Clause — Details →
2.4.167.2 17 Jan 2023 none BSD-2-Clause — Details →
2.4.167.1 16 Jan 2023 none BSD-2-Clause — Details →
2.4.167 22 Dec 2022 none BSD-2-Clause — Details →
2.4.166 02 Dec 2022 none BSD-2-Clause — Details →
2.4.165.1 10 Nov 2022 none BSD-2-Clause — Details →
2.4.165 09 Nov 2022 none BSD-2-Clause — Details →
2.4.162.2 02 Nov 2022 none BSD-2-Clause — Details →
2.4.162.1 02 Oct 2022 none BSD-2-Clause — Details →
2.4.162 23 Sep 2022 none BSD-2-Clause — Details →
2.4.160.1 09 Aug 2022 none BSD-2-Clause — Details →
2.4.160 05 Aug 2022 none BSD-2-Clause — Details →
2.4.159 30 May 2022 none BSD-2-Clause — Details →
2.4.157 24 Mar 2022 none BSD-2-Clause — Details →
2.4.155.1 03 Mar 2022 none BSD-2-Clause — Details →
2.4.155 03 Mar 2022 none BSD-2-Clause — Details →
2.4.152 22 Dec 2021 none BSD-2-Clause — Details →
2.4.151 19 Nov 2021 none BSD-2-Clause — Details →
2.4.148.1 30 Sep 2021 none BSD-2-Clause — Details →
2.4.148 05 Aug 2021 none BSD-2-Clause — Details →
2.4.144 07 Jun 2021 none BSD-2-Clause — Details →
2.4.143 14 May 2021 none BSD-2-Clause — Details →
2.4.142 26 Apr 2021 none BSD-2-Clause — Details →
2.4.141.1 02 Apr 2021 none BSD-2-Clause — Details →
2.4.141 01 Apr 2021 none BSD-2-Clause — Details →
2.4.140 03 Mar 2021 none BSD-2-Clause — Details →
2.4.138 08 Feb 2021 none BSD-2-Clause — Details →
2.4.137.4 04 Feb 2021 none BSD-2-Clause — Details →
2.4.137.3 02 Feb 2021 none BSD-2-Clause — Details →
2.4.137.2 01 Feb 2021 none BSD-2-Clause — Details →
2.4.137.1 21 Jan 2021 none BSD-2-Clause — Details →
2.4.137 20 Jan 2021 none BSD-2-Clause — Details →
2.4.135.3 24 Nov 2020 none BSD-2-Clause — Details →
2.4.135.2 24 Nov 2020 none BSD-2-Clause — Details →
2.4.135.1 24 Nov 2020 none BSD-2-Clause — Details →
2.4.135 23 Nov 2020 none BSD-2-Clause — Details →
2.4.134 02 Nov 2020 none — — Details →
2.4.133 16 Oct 2020 none — — Details →
2.4.131 08 Sep 2020 none — — Details →
2.4.130 20 Aug 2020 none — — Details →
2.4.128 22 Jun 2020 none — — Details →
2.4.127.1 19 Jun 2020 none — — Details →
2.4.127 16 Jun 2020 none — — Details →
2.4.126 18 May 2020 none — — Details →
2.4.125 30 Apr 2020 none — — Details →
2.4.124 31 Mar 2020 none — — Details →
2.4.123 12 Mar 2020 none — — Details →
2.4.122 26 Feb 2020 none — — Details →
2.4.121.1 07 Feb 2020 none — — Details →
2.4.121 06 Feb 2020 none — — Details →
2.4.120 17 Jan 2020 none — — Details →
2.4.119.1 17 Dec 2019 none — — Details →
2.4.119 02 Dec 2019 none — — Details →
2.4.117.3 25 Nov 2019 none — — Details →
2.4.117.2 30 Oct 2019 none — — Details →
2.4.117.1 30 Oct 2019 none — — Details →

The newest 120 of 193 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for pymisp

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 pymisp

Is pymisp safe to use?

Vulert has no vulnerabilities on record for pymisp in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is pymisp's Vulert package health score?

Vulert scores pymisp 78/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 pymisp affected?

No. 2.5.34.4, 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 pymisp should I use?

2.5.34.4 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 pymisp have?

0 vulnerabilities are recorded for pymisp in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new pymisp vulnerabilities disclosed?

0 vulnerabilities were recorded for pymisp in the last 12 months. 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 pymisp 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 pymisp for upcoming vulnerabilities?

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