VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

hydra-core: vulnerability history, versions and safety

hydra-core is a package in the PyPI ecosystem. Vulert records 8 vulnerabilities for it across 58 releases, from Aug 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded H4 U4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
8 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all hydra-core vulnerabilities

Vulert verdict on hydra-core 1.4.0.dev10 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Active

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

  • Current release 1.4.0.dev10 — unaffected i
  • Vulnerabilities on record 8 over 1 year · 8 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 8.5 i
  • With no published fix 0 i
  • Stars 10,708 i
  • Last release 1 month 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 hydra-core, 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
1.4.0rc2 21 Oct 2026 none MIT — Details →
1.4.0rc1 10 Oct 2026 none MIT — Details →
1.3.7 14 Sep 2026 none MIT — Details →
1.4.0.dev10 14 Sep 2026 none MIT — Details →
1.4.0.dev9 30 Aug 2026 U1 MIT Yes Details →
1.3.6 29 Aug 2026 H1 U1 MIT Yes Details →
1.3.5 05 Aug 2026 H3 U3 MIT Yes Details →
1.4.0.dev8 04 Aug 2026 U3 MIT Yes Details →
1.4.0.dev6 19 Jul 2026 U3 MIT Yes Details →
1.3.4 04 Jul 2026 H3 U3 MIT Yes Details →
1.4.0.dev5 27 Jun 2026 U3 MIT Yes Details →
1.4.0.dev4 22 Jun 2026 U3 MIT Yes Details →
1.4.0.dev3 21 Jun 2026 U2 MIT Yes Details →
1.3.3 11 Jun 2026 H2 U2 MIT Yes Details →
1.4.0.dev1 10 Jul 2024 U2 MIT Yes Details →
1.3.2 23 Feb 2023 H2 U2 MIT Yes Details →
1.3.1 21 Dec 2022 H2 U2 MIT Yes Details →
1.3.0 08 Dec 2022 H2 U2 MIT Yes Details →
1.3.0.dev1 29 Nov 2022 H2 U2 MIT Yes Details →
1.3.0.dev0 21 Oct 2022 H2 U2 MIT Yes Details →
1.2.0 17 May 2022 H2 U2 MIT Yes Details →
1.2.0.dev5 15 Apr 2022 H2 U2 MIT Yes Details →
1.2.0.dev4 15 Apr 2022 H2 U2 MIT Yes Details →
1.2.0.dev3 13 Apr 2022 H2 U2 MIT Yes Details →
1.1.2 12 Apr 2022 H2 U2 MIT Yes Details →
1.2.0.dev2 14 Mar 2022 H2 U2 MIT Yes Details →
1.2.0.dev1 23 Feb 2022 H2 U2 MIT Yes Details →
1.1.2.dev0 23 Feb 2022 H2 U2 MIT Yes Details →
1.1.1 19 Aug 2021 H2 U2 MIT Yes Details →
1.0.7 15 Jul 2021 H2 U2 MIT Yes Details →
1.1.0 10 Jun 2021 H2 U2 MIT Yes Details →
1.1.0rc1 13 May 2021 H2 U2 MIT Yes Details →
1.1.0.dev7 10 May 2021 H2 U2 MIT Yes Details →
1.1.0.dev6 28 Apr 2021 H2 U2 MIT Yes Details →
1.1.0.dev5 25 Mar 2021 H2 U2 MIT Yes Details →
1.1.0.dev4 26 Feb 2021 H2 U2 MIT Yes Details →
1.0.6 01 Feb 2021 H2 U2 MIT Yes Details →
1.1.0.dev3 23 Jan 2021 H2 U2 MIT Yes Details →
1.1.0.dev2 08 Jan 2021 H2 U2 MIT Yes Details →
1.0.5 07 Jan 2021 H2 U2 MIT Yes Details →
1.1.0.dev1 01 Jan 2021 H2 U2 MIT Yes Details →
1.0.4 18 Nov 2020 H2 U2 MIT Yes Details →
1.0.3 23 Sep 2020 H2 U2 MIT Yes Details →
1.0.2 20 Sep 2020 H2 U2 MIT Yes Details →
1.0.1 15 Sep 2020 H2 U2 MIT Yes Details →
1.0.0 03 Sep 2020 H2 U2 MIT Yes Details →
1.0.0rc4 18 Aug 2020 H2 U2 MIT Yes Details →
1.0.0rc3 17 Aug 2020 H2 U2 MIT Yes Details →
1.0.0rc2 18 Jul 2020 H2 U2 MIT Yes Details →
1.0.0rc1 31 May 2020 H2 U2 MIT Yes Details →
0.11.3 29 Dec 2019 H2 U2 MIT Yes Details →
0.11.2 04 Dec 2019 H2 U2 MIT Yes Details →
0.11.2rc1 22 Nov 2019 H2 U2 MIT Yes Details →
0.11.1 21 Nov 2019 H2 U2 MIT Yes Details →
0.11.1rc1 21 Nov 2019 H2 U2 MIT Yes Details →
0.11.0 20 Nov 2019 H2 U2 MIT Yes Details →
0.11.0rc1 07 Nov 2019 H2 U2 MIT Yes Details →
0.10.0 19 Oct 2019 H2 U2 MIT Yes Details →
0.9.0 01 Oct 2019 H2 U2 MIT Yes Details →
0.1.5 21 Sep 2019 H2 U2 — Yes Details →
0.1.5rc1 21 Sep 2019 H2 U2 — Yes Details →
0.1.4 19 Sep 2019 H2 U2 — Yes Details →

All 62 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 8

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

03 Vulnerabilities

Recorded vulnerabilities for hydra-core

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-106439: Hydra Package Vulnerability Allows Target Blocklist Bypass 8.5 high 1.3.7 07 Oct 2026
CVE-2026-106439: Hydra Package Vulnerability - Mutable Instantiate Policy Sets Allow Target Blocklist Bypass 8.5 high 1.3.7 15 Oct 2026
CVE-2026-68508: Hydra Code Execution Vulnerability via Untrusted Configuration 7.8 high 1.3.4 21 Aug 2026
CVE-2026-68508: hydra-core Arbitrary Code Execution via Untrusted Config 7.8 high 1.3.4 10 Sep 2026
CVE-2026-106441: Hydra-core Logging Configuration Vulnerability Allows Unsafe Callable Resolution 7.8 high 1.3.6 07 Oct 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 hydra-core

Is hydra-core safe to use?

Vulert records 8 vulnerabilities for hydra-core in PyPI: 0 critical, 4 high, 0 medium and 0 low, plus 4 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 hydra-core's Vulert package health score?

Vulert scores hydra-core 68/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).

Is the latest version of hydra-core affected?

No. 1.4.0.dev10, 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 hydra-core should I use?

1.4.0.dev10 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 hydra-core have?

8 vulnerabilities are recorded for hydra-core in the PyPI ecosystem: 0 critical, 4 high, 0 medium and 0 low, plus 4 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 hydra-core vulnerabilities disclosed?

8 vulnerabilities were recorded for hydra-core in the last 12 months, and the oldest entry in this database dates to 21 Aug 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 hydra-core 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 hydra-core for upcoming vulnerabilities?

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