Vulnerability Database · PyPI · Package report

h5py: vulnerability history, versions and safety

Q: How do I monitor h5py for upcoming vulnerabilities?

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

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

0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all h5py vulnerabilities

Vulert verdict on h5py 3.16.0 i

Updated on 23 Oct 2026

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

Package health score 89/100

Security No known security issues
Maintenance Sustainable
Popularity Key ecosystem project
Community Active

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

Current release 3.16.0 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 12,994 packages i
Stars 2,257 i
OpenSSF scorecard 7/10 i
Last release 7 months ago i
Licence BSD-3-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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for h5py, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
3.16.0	06 Mar 2026	none	BSD-3-Clause	—	Details →
3.15.1	16 Oct 2025	none	BSD-3-Clause	—	Details →
3.15.0	13 Oct 2025	none	BSD-3-Clause	—	Details →
3.14.0	06 Jun 2025	none	BSD-3-Clause	—	Details →
3.13.0	18 Feb 2025	none	BSD-3-Clause	—	Details →
3.12.1	26 Sep 2024	none	BSD-3-Clause	—	Details →
3.12.0	25 Sep 2024	none	BSD-3-Clause	—	Details →
3.11.0	10 Apr 2024	none	BSD-3-Clause	—	Details →
3.10.0	09 Oct 2023	none	BSD-3-Clause	—	Details →
3.9.0	20 Jun 2023	none	BSD-3-Clause	—	Details →
3.8.0	23 Jan 2023	none	BSD-3-Clause	—	Details →
3.7.0	24 May 2022	none	non-standard	—	Details →
3.6.0	16 Nov 2021	none	non-standard	—	Details →
3.5.0	20 Oct 2021	none	non-standard	—	Details →
3.4.0	23 Aug 2021	none	non-standard	—	Details →
3.3.0	22 Jun 2021	none	non-standard	—	Details →
3.2.1	05 Mar 2021	none	non-standard	—	Details →
3.2.0	03 Mar 2021	none	non-standard	—	Details →
3.1.0	06 Nov 2020	none	non-standard	—	Details →
3.0.0	30 Oct 2020	none	non-standard	—	Details →
3.0.0rc1	10 Oct 2020	none	non-standard	—	Details →
2.9.0	08 Dec 2019	none	non-standard	—	Details →
2.10.0	08 Dec 2019	none	non-standard	—	Details →
2.9.0rc1	08 Dec 2018	none	non-standard	—	Details →
2.8.0	06 Jul 2018	none	non-standard	—	Details →
2.8.0rc1	09 Mar 2018	none	non-standard	—	Details →
2.7.1	01 Sep 2017	none	non-standard	—	Details →
2.7.0	19 Mar 2017	none	non-standard	—	Details →
2.7.0rc2	04 Jan 2017	none	non-standard	—	Details →
2.6.0	08 Apr 2016	none	non-standard	—	Details →
2.5.0	08 Apr 2015	none	non-standard	—	Details →
2.4.0	05 Jan 2015	none	non-standard	—	Details →
2.4.0b1	03 Nov 2014	none	non-standard	—	Details →
2.3.1	22 Jun 2014	none	non-standard	—	Details →
2.3.0	22 Apr 2014	none	non-standard	—	Details →
2.3.0b1	14 Mar 2014	none	non-standard	—	Details →
2.2.1	01 Feb 2014	none	non-standard	—	Details →
2.2.1.win32-py2.6	—	none	—	—	Details →
2.2.1.win32-py2.7	—	none	—	—	Details →
2.2.1.win32-py3.2	—	none	—	—	Details →
2.2.1.win32-py3.3	—	none	—	—	Details →
2.3.0.win32-py2.6	—	none	—	—	Details →
2.3.0.win32-py2.7	—	none	—	—	Details →
2.3.0.win32-py3.2	—	none	—	—	Details →
2.3.0.win32-py3.3	—	none	—	—	Details →
2.3.0b1.win32-py2.6	—	none	—	—	Details →
2.3.0b1.win32-py2.7	—	none	—	—	Details →
2.3.0b1.win32-py3.2	—	none	—	—	Details →
2.3.0b1.win32-py3.3	—	none	—	—	Details →
2.3.1.win32-py2.6	—	none	—	—	Details →
2.3.1.win32-py2.7	—	none	—	—	Details →
2.3.1.win32-py3.2	—	none	—	—	Details →
2.3.1.win32-py3.3	—	none	—	—	Details →
2.4.0.win32-py2.6	—	none	—	—	Details →
2.4.0.win32-py2.7	—	none	—	—	Details →
2.4.0.win32-py3.2	—	none	—	—	Details →
2.4.0.win32-py3.3	—	none	—	—	Details →
2.4.0.win32-py3.4	—	none	—	—	Details →
2.4.0b1.win32-py2.6	—	none	—	—	Details →
2.4.0b1.win32-py2.7	—	none	—	—	Details →
2.4.0b1.win32-py3.2	—	none	—	—	Details →
2.4.0b1.win32-py3.3	—	none	—	—	Details →
2.4.0b1.win32-py3.4	—	none	—	—	Details →
2.5.0.win32-py2.6	—	none	—	—	Details →
2.5.0.win32-py2.7	—	none	—	—	Details →
2.5.0.win32-py3.2	—	none	—	—	Details →
2.5.0.win32-py3.3	—	none	—	—	Details →
2.5.0.win32-py3.4	—	none	—	—	Details →

All 68 versions Vulert tracks for this package. 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for h5py

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 h5py

Is h5py safe to use?

Vulert has no vulnerabilities on record for h5py 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 h5py's Vulert package health score?

Vulert scores h5py 89/100, which reads as healthy. 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 h5py affected?

No. 3.16.0, 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 h5py should I use?

3.16.0 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 h5py have?

0 vulnerabilities are recorded for h5py 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 h5py vulnerabilities disclosed?

0 vulnerabilities were recorded for h5py 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 h5py 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 h5py for upcoming vulnerabilities?

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